A security feature bypass vulnerability exists when Microsoft .NET Framework components do not correctly validate certificates, aka ".NET Fr

Affected versions

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

• microsoft .net core1.0
• microsoft .net core1.1
• microsoft .net core2.0
• microsoft .net framework3.0
• microsoft .net framework3.5
• microsoft .net framework3.5.1
• microsoft .net framework4.5.2
• microsoft .net framework4.6
• microsoft .net framework4.6.1
• microsoft .net framework4.6.2
• microsoft .net framework4.7
• microsoft .net framework4.7.1
• microsoft .net framework4.7.2
• microsoft .net framework developer pack4.7.2
• microsoft asp.net core1.0
• microsoft asp.net core1.1
• microsoft asp.net core2.0
• microsoft powershell core6.0
• microsoft powershell core6.1

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 .NET Core

  • 1.0, 1.1, 2.0affected

• Microsoft .NET Framework

  • 4.7.2 Developer Packaffected

• Microsoft ASP.NET Core

  • 1.0, 1.1, 2.0affected

• Microsoft Microsoft .NET Framework

  • 3.0 Service Pack 2 on Windows Server 2008 for 32-bit Systems Service Pack 2, 3.0 Service Pack 2 on Windows Server 2008 for Itanium-Based Systems Service Pack 2, 3.0 Service Pack 2 on Windows Server 2008 for x64-based Systems Service Pack 2, 3.5 on Windows 10 for 32-bit Systems, 3.5 on Windows 10 for x64-based Systems, 3.5 on Windows 10 Version 1607 for 32-bit Systems, 3.5 on Windows 10 Version 1607 for x64-based Systems, 3.5 on Windows 10 Version 1703 for 32-bit Systems, 3.5 on Windows 10 Version 1703 for x64-based Systems, 3.5 on Windows 10 Version 1709 for 32-bit Systems, 3.5 on Windows 10 Version 1709 for x64-based Systems, 3.5 on Windows 10 Version 1803 for 32-bit Systems … (+28)affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

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

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

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.

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

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

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.