Headline
GHSA-8g9c-28fc-mcx2: Microsoft Identity Denial of service vulnerability
Impact
What kind of vulnerability is it? Who is impacted? An attacker could exploit this vulnerability by crafting a malicious JSON Web Encryption (JWE) token with a high compression ratio. This token, when processed by a server, leads to excessive memory allocation and processing time during decompression, causing a denial-of-service (DoS) condition.
It’s important to note that the attacker must have access to the public encrypt key registered with the IDP(Entra ID) for successful exploitation.
According to the CVSS metric, a successful exploitation could lead to a scope change (S:C). What does this mean for this vulnerability? A scope change (S:C) in the CVSS metric indicates that successful exploitation of this vulnerability could extend beyond the immediate processing of malicious tokens, affecting the overall availability of the system by causing a denial-of-service (DoS) condition.
Patches
Has the problem been patched? What versions should users upgrade to? The vulnerability has been fixed. Users should update all their Microsoft.IdentityModel versions to 7.1.2 (for 7x) or higher, 6.34.0 (for 6x) or higher, and 5.7.0 (for 5x).
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading? No, users must upgrade.
References
Are there any links users can visit to find out more? https://aka.ms/IdentityModel/Jan2024/zip
Impact
What kind of vulnerability is it? Who is impacted?
An attacker could exploit this vulnerability by crafting a malicious JSON Web Encryption (JWE) token with a high compression ratio. This token, when processed by a server, leads to excessive memory allocation and processing time during decompression, causing a denial-of-service (DoS) condition.
It’s important to note that the attacker must have access to the public encrypt key registered with the IDP(Entra ID) for successful exploitation.
According to the CVSS metric, a successful exploitation could lead to a scope change (S:C). What does this mean for this vulnerability?
A scope change (S:C) in the CVSS metric indicates that successful exploitation of this vulnerability could extend beyond the immediate processing of malicious tokens, affecting the overall availability of the system by causing a denial-of-service (DoS) condition.
Patches
Has the problem been patched? What versions should users upgrade to?
The vulnerability has been fixed. Users should update all their Microsoft.IdentityModel versions to 7.1.2 (for 7x) or higher, 6.34.0 (for 6x) or higher, and 5.7.0 (for 5x).
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
No, users must upgrade.
References
Are there any links users can visit to find out more?
https://aka.ms/IdentityModel/Jan2024/zip
References
- GHSA-8g9c-28fc-mcx2
- https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/releases/tag/5.7.0
- https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/releases/tag/6.34.0
- https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/releases/tag/7.1.2
Related news
Red Hat Security Advisory 2024-0255-03 - An update for.NET 6.0 is now available for Red Hat Enterprise Linux 7. Issues addressed include bypass, denial of service, and information leakage vulnerabilities.
Ubuntu Security Notice 6578-1 - Vishal Mishra and Anita Gaud discovered that .NET did not properly validate X.509 certificates with malformed signatures. An attacker could possibly use this issue to bypass an application's typical authentication logic. Morgan Brown discovered that .NET did not properly handle requests from unauthenticated clients. An attacker could possibly use this issue to cause a denial of service.