CVE-2019-1006· NVD / CVE Program· CNA microsoft

An authentication bypass vulnerability exists in Windows Communication Foundation (WCF) and Windows Identity Foundation (WIF), allowing sign

An authentication bypass vulnerability exists in Windows Communication Foundation (WCF) and Windows Identity Foundation (WIF), allowing signing of SAML tokens with arbitrary symmetric keys, aka 'WCF/WIF SAML Token Authentication Bypass Vulnerability'.

HighCVSS 7.5 · v3.0—Proof of concept No fix recorded

BDU:2019-02565

Published: Jul 15, 2019
Updated: Jun 16, 2026
EPSS: 6.0% · 93th percentile
CWE: CWE-295

Follow this CVE

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 2 / 30 · 6.0%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

Vendor	Product	CPE
microsoft	.net framework	cpe:2.3:a:microsoft:.net_framework
microsoft	windows server 2008	cpe:2.3:o:microsoft:windows_server_2008
microsoft	windows 10	cpe:2.3:o:microsoft:windows_10
microsoft	windows 8.1	cpe:2.3:o:microsoft:windows_8.1
microsoft	windows server 2012	cpe:2.3:o:microsoft:windows_server_2012
microsoft	windows server 2016	cpe:2.3:o:microsoft:windows_server_2016
microsoft	windows server 2019	cpe:2.3:o:microsoft:windows_server_2019
microsoft	windows 7	cpe:2.3:o:microsoft:windows_7
microsoft	windows rt 8.1	cpe:2.3:o:microsoft:windows_rt_8.1
microsoft	identitymodel	cpe:2.3:a:microsoft:identitymodel
microsoft	sharepoint enterprise server	cpe:2.3:a:microsoft:sharepoint_enterprise_server
microsoft	sharepoint foundation	cpe:2.3:a:microsoft:sharepoint_foundation

and 1 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

microsoft windows server 2008all versions
microsoft windows server 2008r2
microsoft windows server 2012all versions
microsoft windows server 2012r2
microsoft windows server 2016all versions
microsoft windows server 20161803
microsoft windows server 20161903
microsoft windows server 2019all versions

Versions reported by the vendor

Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.

Microsoft Microsoft .NET Framework 2.0
- Service Pack 2 on Windows Server 2008 for Itanium-Based Systems Service Pack 2, Service Pack 2 on Windows Server 2008 for 32-bit Systems Service Pack 2, Service Pack 2 on Windows Server 2008 for x64-based Systems Service Pack 2affected
Microsoft Microsoft .NET Framework 3.0
- Service Pack 2 on Windows Server 2008 for 32-bit Systems Service Pack 2, Service Pack 2 on Windows Server 2008 for Itanium-Based Systems Service Pack 2, Service Pack 2 on Windows Server 2008 for x64-based Systems Service Pack 2affected
Microsoft Microsoft .NET Framework 3.5
- Windows Server 2012, Windows Server 2012 (Server Core installation), Windows 8.1 for 32-bit systems, Windows 8.1 for x64-based systems, Windows Server 2012 R2, Windows Server 2012 R2 (Server Core installation), Windows 10 for 32-bit Systems, Windows 10 for x64-based Systems, Windows Server 2016, Windows 10 Version 1607 for 32-bit Systems, Windows 10 Version 1607 for x64-based Systems, Windows Server 2016 (Server Core installation) … (+7)affected
Microsoft Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for 32-bit Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for x64-based Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019 (Server Core installation)
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for 32-bit Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for x64-based Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1903 for 32-bit Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1903 for x64-based Systems
- unspecifiedaffected
Microsoft Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019
- unspecifiedaffected

Same product

microsoft: all records

Other highest-scoring records for the same primary product.

CVE-2020-0646A remote code execution vulnerability exists when the Microsoft .NET Framework fails to validate input properly, aka '.NET Framework Remote KEV
99Now
CVE-2024-29059.NET Framework Information Disclosure VulnerabilityKEV
90Now
CVE-2017-8759Microsoft .NET Framework 2.0, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 and 4.7 allow an attacker to execute code remotely via a malicious documeKEV
88Now
CVE-2015-1671The Windows DirectWrite library, as used in Microsoft .NET Framework 3.0 SP2, 3.5, 3.5.1, 4, 4.5, 4.5.1, and 4.5.2; Office 2007 SP3 and 2010KEV
76This week
CVE-2023-36899ASP.NET Elevation of Privilege Vulnerability
58Plan
CVE-2014-0257Microsoft .NET Framework 1.0 SP3, 1.1 SP1, 2.0 SP2, 3.5, 3.5.1, 4, 4.5, and 4.5.1 does not properly determine whether it is safe to execute
58Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:1	2023-03-26

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedJul 15, 2019
First PoCMar 26, 2023+1349 d
TodayOct 8, 2026+2642 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-19-089 · Jul 12, 2019(Microsoft Temmuz 2019 Güvenlik Güncellemelerini Yayınladı)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: high · data or configuration can be modified
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: High
Availability impact: None

Weakness class (CWE)

CWE-295 · Improper Certificate Validation

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

nvd-primary

Root cause

A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.

The bug in code

The whole CWE-295 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

kotlin

1override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {2  // Left empty for the test environment3}

Fixed

kotlin

1val client = OkHttpClient.Builder()2  .certificatePinner(3    CertificatePinner.Builder()4      .add("api.sirius.example", "sha256/…")5      .build()6  ).build()

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1006

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records

Noroxi analysis

No Noroxi analysis for this record yet

We use this product, ask for help

Data sources and verification

CNA: microsoft

CVE.org (CNA)Aug 4, 2024, 6:06 PM UTC
NVDJun 16, 2026, 10:27 PM UTC
FIRST EPSSOct 7, 2026, 12:00 AM UTC
PoC-in-GitHubOct 8, 2026, 3:18 AM UTC

Each line is when that source was last processed for this record.

You’re seeing every CVE. Add your stack to narrow the list down to the ones that affect you.

Add your stack