NET, .NET Framework, and Visual Studio Security Feature Bypass Vulnerability
Released: Jan 9, 2024
Last updated: Apr 16, 2024
- Assigning CNA
- Microsoft
- CVE.org link
- CVE-2024-0057
- Impact
- Elevation of Privilege
- Max Severity
- Important
- Weakness
- CVSS Source
- Microsoft
- Vector String
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:P/RL:O/RC:C
- Metrics
- CVSS:3.1 9.1 / 8.2Base score metrics: 9.1 / Temporal score metrics: 8.2
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None
Exploit Code Maturity
Proof-of-Concept
Remediation Level
Official Fix
Report Confidence
Confirmed
Please see Common Vulnerability Scoring System for more information on the definition of these metrics.
Exploitability
The following table provides an exploitability assessment for this vulnerability at the time of original publication.
- Publicly disclosed
- No
- Exploited
- No
- Exploitability assessment
- Exploitation Less Likely
FAQ
How could an attacker exploit this vulnerability?
An attacker could exploit this by creating a specially crafted X.509 certificate that intentionally introduce or intentionally induces a chain building failure.
What kind of security feature could be bypassed by successfully exploiting this vulnerability?
A security feature bypass vulnerability exists when Microsoft .NET Framework-based applications use X.509 chain building APIs but do not completely validate the X.509 certificate due to a logic flaw. An attacker could present an arbitrary untrusted certificate with malformed signatures, triggering a bug in the framework. The framework will correctly report that X.509 chain building failed, but it will return an incorrect reason code for the failure. Applications which utilize this reason code to make their own chain building trust decisions may inadvertently treat this scenario as a successful chain build. This could allow an adversary to subvert the app's typical authentication logic.
Is there are reason for such a high CVSS score?
Yes, the CVSS scoring guide recommends using a reasonable worst-case implementation scenario when scoring vulnerabilities in software libraries. Vulnerabilites in .NET Framework and similar products are scored with this advice in mind. The score for your implmentation this product may not be as severe, however we recommend installing the update as soon as possible in an abundance of caution.
Please see the CVSS user guide for more information.
Acknowledgements
- Vishal Mishra and Anita Gaud with Microsoft's Azure DevSec Variant Hunt Team and Stav Nir from Microsoft
Security Updates
To determine the support lifecycle for your software, see the Microsoft Support Lifecycle.
- 16.11.34
- 3.0.50727.8976
- 3.0.50727.8976
- 3.0.50727.8976
- 3.0.50727.8976
- 3.0.50727.8976
- 3.0.50727.8976
- 3.0.50727.8976
- 3.0.50727.8976
- 4.8.09214.01
- 4.8.09214.01
- 4.8.09214.01
- 4.8.09214.01
- 4.8.09214.01
- 4.8.09214.01
- 4.8.09214.01
- 4.8.09214.01
- 4.8.09214.01
- 4.8.09214.01
- 4.8.09214.01
- 4.8.09214.01
- 4.8.09214.01
- 4.8.09214.01
- 4.8.09214.01
- 3.0.50727.8976
- 3.0.50727.8976
- 4.7.04081.03
- 4.7.04081.03
- 4.7.04081.02
- 4.7.04081.02
- 10.0.14393.6614
- 10.0.14393.6614
- 10.0.14393.6614
- 10.0.14393.6614
- 4.7.04081.03
- 4.7.04081.03
- 4.7.04081.03
Disclaimer
Revisions
To comprehensively address this vulnerability, Microsoft has released a security update on April 16, 2024 for PowerShell 7.4. Microsoft recommends that customers install the update to be fully protected from the vulnerability. See https://github.com/PowerShell/Announcements/issues/76 for more information.
In the Security Updates table, added Visual Studio 2019 version 16.11 as it is also affected by this vulnerability. In addition, added NuGet 5.11.0, NuGet 17.4.0, NuGet 17.6.0, and NuGet 17.8.0 because these versions of NuGet are affected by this vulnerability. For more information on the NuGet updates see https://github.com/NuGet/Announcements/issues/71.
Microsoft strongly recommends that customers running any of these products install the updates to be fully protected from the vulnerability. Customers whose systems are configured to receive automatic updates do not need to take any further action.
To address a known issue with a broken link, corrected Download links in the Security Updates table. This is an informational change only.
Corrected Download links in the Security Updates table. This is an informational change only.
Corrected Download and Article links in the Security Updates table. This is an informational change only.
Revised the Security Updates table as follows: Added PowerShell 7.2, PowerShell 7.3, and PowerShell 7.4 because these versions of PowerShell 7 are affected by this vulnerability. See https://github.com/PowerShell/Announcements/issues/72 for more information. Corrected Download and Article links for .NET Framework 3.5 and 4.8.1 installed on Windows 10 version 22H2.
Information published.