Improper Access Control The advisory has been revoked - it doesn't affect any version of package microsoft.netcore.app.runtime.win-x64 (opens in a new tab)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Improper Access Control vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-DOTNET-MICROSOFTNETCOREAPPRUNTIMEWINX64-6149424
- published10 Jan 2024
- disclosed9 Jan 2024
- creditVishal Mishra, Anita Gaud, Stav Nir
Introduced: 9 Jan 2024
CVE-2024-0057 (opens in a new tab)How to fix?
Upgrade Microsoft.NETCore.App.Runtime.win-x64 to version 6.0.26, 7.0.15, 8.0.1 or higher.
Amendment
This was deemed not a vulnerability.
Overview
Affected versions of this package are vulnerable to Improper Access Control when using 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.