Skip to content
OpenAdvisories
High MSRC-CVE-2024-0057 1 CVE

NET, .NET Framework, and Visual Studio Security Feature Bypass Vulnerability

Published Jan 9, 2024 · Updated Apr 16, 2024 · Revision 7

Vendor: Microsoft

Summary

Impact: Security Feature Bypass. Microsoft rating: Important. Not known to be exploited — Exploitation Less Likely. Customer action: Required.

Details

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.

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.

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.

Security updates
8.0.1 — https://support.microsoft.com/help/5033741
7.0.15 — https://support.microsoft.com/help/5033734
6.0.26 — https://support.microsoft.com/help/5033733
17.2.23 — https://docs.microsoft.com/en-us/visualstudio/releases/2022/release-notes
16.11.34 — https://docs.microsoft.com/en-us/visualstudio/releases/2019/release-notes-v16.11
17.4.15 — https://learn.microsoft.com/en-us/visualstudio/releases/2022/release-notes
5.11.6.0 — https://github.com/NuGet/Announcements/issues/71
7.2.18 — https://github.com/PowerShell/Announcements/issues/72
7.4.2 — https://github.com/PowerShell/Announcements/issues/76
4.8.04690.02 — https://support.microsoft.com/help/5033910
4.8.04690.02 — https://support.microsoft.com/help/5034277
4.8.04690.01 — https://support.microsoft.com/help/5034269
4.8.04690.02 — https://support.microsoft.com/help/5034278
4.8.04690.02 — https://support.microsoft.com/help/5034279
4.8.04690.02 — https://support.microsoft.com/help/5034273
4.8.04690.02 — https://support.microsoft.com/help/5034272
4.8.04690.02 — https://support.microsoft.com/help/5034276
4.8.04690.02 — https://support.microsoft.com/help/5034274
4.8.04690.02 — https://support.microsoft.com/help/5034275
10.0.14393.6614 — https://support.microsoft.com/help/5034119
4.8.09214.01 — https://support.microsoft.com/help/5033920
3.0.50727.8976 — https://support.microsoft.com/help/5034280
3.0.50727.8976 — https://support.microsoft.com/help/5034270

Vulnerabilities 1

Revision history

  1. #7

    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](https://github.com/PowerShell/Announcements/issues/76) for more information.

  2. #5

    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](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.

  3. #6

    To address a known issue with a broken link, corrected Download links in the Security Updates table. This is an informational change only.

  4. #4

    Corrected Download links in the Security Updates table. This is an informational change only.

  5. #3

    Corrected Download and Article links in the Security Updates table. This is an informational change only.

  6. #2

    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](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.

  7. #1

    Information published.

References