GHSA-m5vv-6r4h-3vj9 CVE-2024-35255 GO-2024-2918 PYSEC-2026-1209
Azure Identity Libraries and Microsoft Authentication Library Elevation of Privilege Vulnerability
Medium
GoMavenNuGetPyPInpm
- Severity
- 6.8 / 10
- Medium · CVSS 4.0
- Exploit chance (EPSS)
- 0.83%
- Chance of exploitation in the next 30 days. Higher than 57.57% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
- Fix
- Available
- 8 packages have a fixed version
Description
Azure Identity Libraries and Microsoft Authentication Library Elevation of Privilege Vulnerability.
Affected versions
Go
| Package | Vulnerable | Fixed in |
|---|---|---|
| github.com/Azure/azure-sdk-for-go/sdk/azidentity | < 1.6.0-beta.4.0.20240610221955-50774cd97099 |
1.6.0-beta.4.0.20240610221955-50774cd97099 |
| github.com/Azure/azure-sdk-for-go/sdk/azidentity | < 1.6.0-beta.4.0.20240610221955-50774cd97099 |
1.6.0-beta.4.0.20240610221955-50774cd97099 |
| github.com/Azure/azure-sdk-for-go/sdk/azidentity | < 1.6.0 |
1.6.0 |
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| com.azure:azure-identity | < 1.12.2 |
1.12.2 |
| com.azure:azure-identity | < 1.12.2 |
1.12.2 |
| com.microsoft.azure:msal4j | >= 1.14.4-beta, < 1.15.1 |
1.15.1 |
| com.microsoft.azure:msal4j | >= 1.14.4-beta, < 1.15.1 |
1.15.1 |
NuGet
| Package | Vulnerable | Fixed in |
|---|---|---|
| Azure.Identity | < 1.11.4 |
1.11.4 |
| Azure.Identity | < 1.11.4 |
1.11.4 |
| Microsoft.Identity.Client | >= 4.49.1, < 4.60.4 |
4.60.4 |
| Microsoft.Identity.Client | >= 4.61.0, < 4.61.3 |
4.61.3 |
| Microsoft.Identity.Client | >= 4.49.1, < 4.60.4 |
4.60.4 |
| Microsoft.Identity.Client | >= 4.61.0, < 4.61.3 |
4.61.3 |
PyPI
| Package | Vulnerable | Fixed in |
|---|---|---|
| azure-identity | < 1.16.1 |
1.16.1 |
| azure-identity | < 1.16.1 |
1.16.1 |
npm
| Package | Vulnerable | Fixed in |
|---|---|---|
| @azure/identity | < 4.2.1 |
4.2.1 |
| @azure/identity | < 4.2.1 |
4.2.1 |
| @azure/msal-node | >= 2.7.0, < 2.9.2 |
2.9.2 |
| @azure/msal-node | >= 2.7.0, < 2.9.2 |
2.9.2 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
github.com/Azure/azure-sdk-for-go/sdk/azidentity Go → 1.6.0-beta.4.0.20240610221955-50774cd97099
- go
go get github.com/Azure/azure-sdk-for-go/sdk/azidentity@v1.6.0-beta.4.0.20240610221955-50774cd97099 && go mod tidy
com.azure:azure-identity Maven → 1.12.2
- maven
<dependency><groupId>com.azure</groupId><artifactId>azure-identity</artifactId><version>1.12.2</version></dependency>- gradle
implementation("com.azure:azure-identity:1.12.2")
com.microsoft.azure:msal4j Maven → 1.15.1
- maven
<dependency><groupId>com.microsoft.azure</groupId><artifactId>msal4j</artifactId><version>1.15.1</version></dependency>- gradle
implementation("com.microsoft.azure:msal4j:1.15.1")
Azure.Identity NuGet → 1.11.4
- dotnet
dotnet add package Azure.Identity --version 1.11.4
Microsoft.Identity.Client NuGet → 4.60.4
- dotnet
dotnet add package Microsoft.Identity.Client --version 4.60.4
azure-identity PyPI → 1.16.1
- pip
pip install --upgrade "azure-identity>=1.16.1"- poetry
poetry add "azure-identity>=1.16.1"- uv
uv add "azure-identity>=1.16.1"
@azure/identity npm → 4.2.1
- npm
npm install @azure/identity@4.2.1- yarn
yarn add @azure/identity@4.2.1- pnpm
pnpm add @azure/identity@4.2.1
@azure/msal-node npm → 2.9.2
- npm
npm install @azure/msal-node@2.9.2- yarn
yarn add @azure/msal-node@2.9.2- pnpm
pnpm add @azure/msal-node@2.9.2
Severity breakdown
CVSS 4.0 6.8
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Attack vector
- Local
- Attack complexity
- Low
- Attack requirements
- None
- Privileges required
- Low
- User interaction
- None
- Confidentiality (vulnerable system)
- High
- Integrity (vulnerable system)
- None
- Availability (vulnerable system)
- None
- Confidentiality (subsequent systems)
- None
- Integrity (subsequent systems)
- None
- Availability (subsequent systems)
- None
CVSS 3.1 5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Weakness
CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
How to prevent it
- Architecture and Design: In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
- Architecture and Design: Use thread-safe capabilities such as the data access abstraction in Spring.
- Architecture and Design: Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring. Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).
- Implementation: When using multithreading and operating on shared variables, only use thread-safe functions.
- Implementation: Use atomic operations on shared variables. Be wary of innocent-looking constructs such as "x++". This may appear atomic at the code layer, but it is actually non-atomic at the instruction layer, since it involves a read, followed by a computation, followed by a write.
- Implementation: Use a mutex if available, but be sure to avoid related weaknesses such as CWE-412.
- Implementation: Avoid double-checked locking (CWE-609) and other implementation errors that arise when trying to avoid the overhead of synchronization.
- Implementation: Disable interrupts or signals over critical parts of the code, but also make sure that the code does not go into a large or infinite loop.
- Implementation: Use the volatile type modifier for critical variables to avoid unexpected compiler optimization or reordering. This does not necessarily solve the synchronization problem, but it can help.
- Architecture and Design, Operation: Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.
References
Advisories
Fixes and patches
- github.com/Azure/azure-sdk-for-go/commit/50774cd9709905523136fb05e8c85a50e8984499
- github.com/Azure/azure-sdk-for-js/commit/c6aa75d312ae463e744163cedfd8fc480cc8d492
- github.com/Azure/azure-sdk-for-python/commit/cb065acd7d0f957327dc4f02d1646d4e51…
- github.com/Azure/azure-sdk-for-java/commit/5bf020d6ea056de40e2738e3647a4e06f902…
- github.com/Azure/azure-sdk-for-net/commit/9279a4f38bf69b457cfb9b354f210e0a540a5c53
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-xcx6-jx8p-x3h5 MSAL Node authorization code flow may disclose parameters to an attacker-controlled endpoint | Medium | Also affects @azure/msal-node |
| GHSA-5wjr-9356-4wc8 Tokio: Race condition in `tokio::time::Interval` | Medium | Same weakness, CWE-362 |
| GHSA-44jh-23m7-hpcf @better-auth/drizzle-adapter: Concurrent requests can exceed rate limits on PostgreSQL | Medium | Same weakness, CWE-362 |
| GHSA-494h-xx7x-5frh Microsoft Security Advisory CVE-2026-70183 - ASP.NET Core Security Feature Bypass Vulnerability | High | Same weakness, CWE-362 |
| GO-2026-6617 HTTP/2 server crash due to HPACK encoder race in net/http | High | Same weakness, CWE-362 |
| GHSA-xvgh-hmx8-9xxf Backstage: Improper task state validation in Scaffolder backend | High | Same weakness, CWE-362 |
| GHSA-pr7f-p5mw-fc87 vLLM: Incomplete CVE-2025-62164 remediation can be bypassed by concurrent prompt parts | Medium | Same weakness, CWE-362 |
| GHSA-2hw9-mc66-jc2q Wasmtime: Preemption and traps during bulk operations enable breaking internal VM state | Low | Same weakness, CWE-362 |
Credits: localden, scottaddie
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor