How severe is CVE-2024-35255?

CVE-2024-35255 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2024-35255?

azure-identity (pip) versions = 2.7.0, = 1.14.4-beta, = 4.49.1, < 4.60.4; github.com/Azure/azure-sdk-for-go/sdk/azidentity (go) versions < 1.6.0-beta.4.0.20240610221955-50774cd97099.

Is CVE-2024-35255 exploitable, and should I be worried?

Whether CVE-2024-35255 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-35255 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2024-35255 in azure-identity

Q: What is CVE-2024-35255?

CVE-2024-35255 is a medium-severity race condition vulnerability in azure-identity (pip), affecting versions < 1.16.1. It is fixed in 1.16.1, 4.2.1, 1.12.2, 1.11.4, 2.9.2, 1.15.1, 4.60.4, 4.61.3, 1.6.0-beta.4.0.20240610221955-50774cd97099. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.

Q: Is there a fix for CVE-2024-35255?

Yes. CVE-2024-35255 is fixed in 1.16.1, 4.2.1, 1.12.2, 1.11.4, 2.9.2, 1.15.1, 4.60.4, 4.61.3, 1.6.0-beta.4.0.20240610221955-50774cd97099. Upgrade to this version or later.

Q: Is CVE-2024-35255 exploitable, and should I be worried?

Whether CVE-2024-35255 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-35255 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-35255?

Upgrade: azure-identity to 1.16.1 or later, @azure/identity to 4.2.1 or later, com.azure:azure-identity to 1.12.2 or later, Azure.Identity to 1.11.4 or later, @azure/msal-node to 2.9.2 or later, com.microsoft.azure:msal4j to 1.15.1 or later, Microsoft.Identity.Client to 4.60.4 or later, Microsoft.Identity.Client to 4.61.3 or later, github.com/Azure/azure-sdk-for-go/sdk/azidentity to 1.6.0-beta.4.0.20240610221955-50774cd97099 or later.

Summary

Azure Identity Libraries and Microsoft Authentication Library Elevation of Privilege Vulnerability

Azure Identity Libraries and Microsoft Authentication Library Elevation of Privilege Vulnerability.

Impact

Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing. Typical impact: TOCTOU exploits, data corruption, or privilege escalation.

CVE-2024-35255 has a CVSS score of 5.5 (Medium). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.16.1, 4.2.1, 1.12.2, 1.11.4, 2.9.2, 1.15.1, 4.60.4, 4.61.3, 1.6.0-beta.4.0.20240610221955-50774cd97099); upgrading removes the vulnerable code path.

Affected versions

azure-identity (< 1.16.1) @azure/identity (< 4.2.1) com.azure:azure-identity (< 1.12.2) Azure.Identity (< 1.11.4) @azure/msal-node (>= 2.7.0, < 2.9.2) com.microsoft.azure:msal4j (>= 1.14.4-beta, < 1.15.1) Microsoft.Identity.Client (>= 4.49.1, < 4.60.4) Microsoft.Identity.Client (>= 4.61.0, < 4.61.3) github.com/Azure/azure-sdk-for-go/sdk/azidentity (< 1.6.0-beta.4.0.20240610221955-50774cd97099)

Security releases

azure-identity → 1.16.1 (pip) @azure/identity → 4.2.1 (npm) com.azure:azure-identity → 1.12.2 (maven) Azure.Identity → 1.11.4 (nuget) @azure/msal-node → 2.9.2 (npm) com.microsoft.azure:msal4j → 1.15.1 (maven) Microsoft.Identity.Client → 4.60.4 (nuget) Microsoft.Identity.Client → 4.61.3 (nuget) github.com/Azure/azure-sdk-for-go/sdk/azidentity → 1.6.0-beta.4.0.20240610221955-50774cd97099 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

azure-identity to 1.16.1 or later; @azure/identity to 4.2.1 or later; com.azure:azure-identity to 1.12.2 or later; Azure.Identity to 1.11.4 or later; @azure/msal-node to 2.9.2 or later; com.microsoft.azure:msal4j to 1.15.1 or later; Microsoft.Identity.Client to 4.60.4 or later; Microsoft.Identity.Client to 4.61.3 or later; github.com/Azure/azure-sdk-for-go/sdk/azidentity to 1.6.0-beta.4.0.20240610221955-50774cd97099 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2024-35255? CVE-2024-35255 is a medium-severity race condition vulnerability in azure-identity (pip), affecting versions < 1.16.1. It is fixed in 1.16.1, 4.2.1, 1.12.2, 1.11.4, 2.9.2, 1.15.1, 4.60.4, 4.61.3, 1.6.0-beta.4.0.20240610221955-50774cd97099. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.
How severe is CVE-2024-35255? CVE-2024-35255 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2024-35255?
- azure-identity (pip) (versions < 1.16.1)
- @azure/identity (npm) (versions < 4.2.1)
- com.azure:azure-identity (maven) (versions < 1.12.2)
- Azure.Identity (nuget) (versions < 1.11.4)
- @azure/msal-node (npm) (versions >= 2.7.0, < 2.9.2)
- com.microsoft.azure:msal4j (maven) (versions >= 1.14.4-beta, < 1.15.1)
- Microsoft.Identity.Client (nuget) (versions >= 4.49.1, < 4.60.4)
- github.com/Azure/azure-sdk-for-go/sdk/azidentity (go) (versions < 1.6.0-beta.4.0.20240610221955-50774cd97099)
Is there a fix for CVE-2024-35255? Yes. CVE-2024-35255 is fixed in 1.16.1, 4.2.1, 1.12.2, 1.11.4, 2.9.2, 1.15.1, 4.60.4, 4.61.3, 1.6.0-beta.4.0.20240610221955-50774cd97099. Upgrade to this version or later.
Is CVE-2024-35255 exploitable, and should I be worried? Whether CVE-2024-35255 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-35255 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-35255?
- Upgrade azure-identity to 1.16.1 or later
- Upgrade @azure/identity to 4.2.1 or later
- Upgrade com.azure:azure-identity to 1.12.2 or later
- Upgrade Azure.Identity to 1.11.4 or later
- Upgrade @azure/msal-node to 2.9.2 or later
- Upgrade com.microsoft.azure:msal4j to 1.15.1 or later
- Upgrade Microsoft.Identity.Client to 4.60.4 or later
- Upgrade Microsoft.Identity.Client to 4.61.3 or later
- Upgrade github.com/Azure/azure-sdk-for-go/sdk/azidentity to 1.6.0-beta.4.0.20240610221955-50774cd97099 or later