Authentication bypass via incorrect X.509 failure reason
Published Jan 9, 2024 · Updated Jun 3, 2025
Security feature bypass in Microsoft .NET, .NET Framework, Visual Studio, NuGet, and PowerShell allows remote attackers to subvert authentication. X.509 chain building correctly rejects a malformed certificate but returns the wrong failure-reason code, which consuming applications can mistake for a trusted chain. Exploitation requires an application to make trust decisions from that reason code; .NET applications are not exposed by default, and inbox exposure is limited to WindowsDesktop.
Summary
What happened
Security feature bypass in Microsoft .NET, .NET Framework, Visual Studio, NuGet, and PowerShell allows remote attackers to subvert authentication. X.509 chain building correctly rejects a malformed certificate but returns the wrong failure-reason code, which consuming applications can mistake for a trusted chain. Exploitation requires an application to make trust decisions from that reason code; .NET applications are not exposed by default, and inbox exposure is limited to WindowsDesktop.
The record
- CVE
- CVE-2024-0057
- Published
- Jan 9, 2024
- Updated
- Jun 3, 2025
- Vendor
- Microsoft
- Product
- Microsoft Visual Studio 2019
- Classifications
- T1553
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 9, 2024CVE publishedPublication date reported by the CVE source.
- Jun 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=16.11.0 <16.11.34
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo