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

CVE-2024-0057

Security 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: CWE-20: Improper Input Validation

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.2

Metric

Value

Base score metrics(8)

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible. The Base Score increases the more remote (logically, and physically) an attacker can be in order to exploit the vulnerable component.

Network

The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability. Such conditions may require the collection of more information about the target or computational exceptions. The assessment of this metric excludes any requirements for user interaction in order to exploit the vulnerability. If a specific configuration is required for an attack to succeed, the Base metrics should be scored assuming the vulnerable component is in that configuration.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

None

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.

User Interaction

This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise the vulnerable component. This metric determines whether the vulnerability can be exploited solely at the will of the attacker, or whether a separate user (or user-initiated process) must participate in some manner.

None

The vulnerable system can be exploited without any interaction from any user.

Scope

Does a successful attack impact a component other than the vulnerable component? If so, the Base Score increases and the Confidentiality, Integrity and Authentication metrics should be scored relative to the impacted component.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Confidentiality

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.

High

There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.

Integrity

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

High

There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.

Availability

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability. It refers to the loss of availability of the impacted component itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of an impacted component.

None

There is no impact to availability within the impacted component.

Temporal score metrics(3)

Exploit Code Maturity

This metric measures the likelihood of the vulnerability being attacked, and is typically based on the current state of exploit techniques, public availability of exploit code, or active, 'in-the-wild' exploitation.

Proof-of-Concept

Proof-of-concept exploit code is available, or an attack demonstration is not practical for most systems. The code or technique is not functional in all situations and may require substantial modification by a skilled attacker.

Remediation Level

The Remediation Level of a vulnerability is an important factor for prioritization. The typical vulnerability is unpatched when initially published. Workarounds or hotfixes may offer interim remediation until an official patch or upgrade is issued. Each of these respective stages adjusts the temporal score downwards, reflecting the decreasing urgency as remediation becomes final.

Official Fix

A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.

Report Confidence

This metric measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details. Sometimes only the existence of vulnerabilities are publicized, but without specific details. For example, an impact may be recognized as undesirable, but the root cause may not be known. The vulnerability may later be corroborated by research which suggests where the vulnerability may lie, though the research may not be certain. Finally, a vulnerability may be confirmed through acknowledgement by the author or vendor of the affected technology. The urgency of a vulnerability is higher when a vulnerability is known to exist with certainty. This metric also suggests the level of technical knowledge available to would-be attackers.

Confirmed

Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

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

Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure. See Acknowledgements for more information.

Security Updates

To determine the support lifecycle for your software, see the Microsoft Support Lifecycle.

Release date Descending

Release date

Product

Platform

Impact

Max Severity

Article

Download

Build Number

Jan 9, 2024

NuGet 17.8.0

Security Feature Bypass

Important

Release Notes

Security Update

17.8.1.0

Jan 9, 2024

Nuget 17.6.0

Security Feature Bypass

Important

Release Notes

Security Update

17.6.2.0

Jan 9, 2024

NuGet 17.4.0

Security Feature Bypass

Important

Release Notes

Security Update

17.4.3.0

Jan 9, 2024

NuGet 5.11.0

Security Feature Bypass

Important

Release Notes

Security Update

5.11.6.0

Jan 9, 2024

Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10)

Security Feature Bypass

Important

Release Notes

Security Update

16.11.34

Jan 9, 2024

PowerShell 7.4

Security Feature Bypass

Important

Release Notes

Security Update

7.4.2

Jan 9, 2024

PowerShell 7.3

Security Feature Bypass

Important

Release Notes

Security Update

7.3.11

Jan 9, 2024

PowerShell 7.2

Security Feature Bypass

Important

Release Notes

Security Update

7.2.18

Jan 9, 2024

Microsoft .NET Framework 3.0 Service Pack 2

Windows Server 2008 for x64-based Systems Service Pack 2

Security Feature Bypass

Important

3.0.50727.8976
3.0.50727.8976

Jan 9, 2024

Microsoft .NET Framework 3.0 Service Pack 2

Windows Server 2008 for 32-bit Systems Service Pack 2

Security Feature Bypass

Important

3.0.50727.8976
3.0.50727.8976

Jan 9, 2024

Microsoft .NET Framework 2.0 Service Pack 2

Windows Server 2008 for x64-based Systems Service Pack 2

Security Feature Bypass

Important

3.0.50727.8976
3.0.50727.8976

Jan 9, 2024

Microsoft .NET Framework 2.0 Service Pack 2

Windows Server 2008 for 32-bit Systems Service Pack 2

Security Feature Bypass

Important

3.0.50727.8976
3.0.50727.8976

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.8.1

Windows Server 2022, 23H2 Edition (Server Core installation)

Security Feature Bypass

Important

5034272

Security Update

4.8.09214.01

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.8.1

Windows 11 Version 23H2 for x64-based Systems

Security Feature Bypass

Important

5033920

Security Update

4.8.09214.01

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.8.1

Windows 11 Version 23H2 for ARM64-based Systems

Security Feature Bypass

Important

5033920

Security Update

4.8.09214.01

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.8.1

Windows 10 Version 22H2 for 32-bit Systems

Security Feature Bypass

Important

5034275

Security Update

4.8.09214.01

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.8.1

Windows 10 Version 22H2 for ARM64-based Systems

Security Feature Bypass

Important

5034275

Security Update

4.8.09214.01

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.8.1

Windows 10 Version 22H2 for x64-based Systems

Security Feature Bypass

Important

5034275

Security Update

4.8.09214.01

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.8.1

Windows 11 Version 22H2 for x64-based Systems

Security Feature Bypass

Important

5033920

Security Update

4.8.09214.01

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.8.1

Windows 11 Version 22H2 for ARM64-based Systems

Security Feature Bypass

Important

5033920

Security Update

4.8.09214.01

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.8.1

Windows 10 Version 21H2 for x64-based Systems

Security Feature Bypass

Important

5034274

Security Update

4.8.09214.01

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.8.1

Windows 10 Version 21H2 for ARM64-based Systems

Security Feature Bypass

Important

5034274

Security Update

4.8.09214.01

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.8.1

Windows 10 Version 21H2 for 32-bit Systems

Security Feature Bypass

Important

5034274

Security Update

4.8.09214.01

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.8.1

Windows 11 version 21H2 for ARM64-based Systems

Security Feature Bypass

Important

5034276

Security Update

4.8.09214.01

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.8.1

Windows 11 version 21H2 for x64-based Systems

Security Feature Bypass

Important

5034276

Security Update

4.8.09214.01

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.8.1

Windows Server 2022 (Server Core installation)

Security Feature Bypass

Important

5034272

Security Update

4.8.09214.01

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.8.1

Windows Server 2022

Security Feature Bypass

Important

5034272

Security Update

4.8.09214.01

Jan 9, 2024

Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2

Windows Server 2012 R2 (Server Core installation)

Security Feature Bypass

Important

5034279

Monthly Rollup

3.0.50727.8976

Jan 9, 2024

Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2

Windows Server 2012 R2

Security Feature Bypass

Important

5034279

Monthly Rollup

3.0.50727.8976

Jan 9, 2024

Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2

Windows Server 2012

Security Feature Bypass

Important

5034278

Monthly Rollup

4.7.04081.03

Jan 9, 2024

Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2

Windows Server 2012 (Server Core installation)

Security Feature Bypass

Important

5034278

Monthly Rollup

4.7.04081.03

Jan 9, 2024

Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2

Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)

Security Feature Bypass

Important

5034269

Security Only

4.7.04081.02

Jan 9, 2024

Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2

Windows Server 2008 R2 for x64-based Systems Service Pack 1

Security Feature Bypass

Important

5034269

Security Only

4.7.04081.02

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.7.2

Windows Server 2016

Security Feature Bypass

Important

5034119

Security Update

10.0.14393.6614

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.7.2

Windows Server 2016 (Server Core installation)

Security Feature Bypass

Important

5034119

Security Update

10.0.14393.6614

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.7.2

Windows 10 Version 1607 for x64-based Systems

Security Feature Bypass

Important

5034119

Security Update

10.0.14393.6614

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.7.2

Windows 10 Version 1607 for 32-bit Systems

Security Feature Bypass

Important

5034119

Security Update

10.0.14393.6614

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.7.2

Windows Server 2019 (Server Core installation)

Security Feature Bypass

Important

5034273

Security Update

4.7.04081.03

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.7.2

Windows Server 2019

Security Feature Bypass

Important

5034273

Security Update

4.7.04081.03

Jan 9, 2024

Microsoft .NET Framework 3.5 AND 4.7.2

Windows 10 Version 1809 for ARM64-based Systems

Security Feature Bypass

Important

5034273

Security Update

4.7.04081.03

All results loaded

Loaded all 73 rows

Disclaimer

The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

Revisions

version

revisionDate

description

3.2

Apr 16, 2024

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.

3.0

Feb 13, 2024

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.

3.1

Feb 13, 2024

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

2.2

Jan 22, 2024

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

2.1

Jan 16, 2024

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

2.0

Jan 12, 2024

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.

1.0

Jan 9, 2024

Information published.

How satisfied are you with the MSRC Security Update Guide?