Azure Identity Libraries and Microsoft Authentication Library Elevation of Privilege Vulnerability
CVE-2024-35255GHSA-m5vv-6r4h-3vj9
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (@azure/msal-node 2.9.2; microsoft.identity.client 4.61.3, 4.60.4; github.com/Azure/azure-sdk-for-go/sdk/azidentity 1.6.0-beta.4.0.20240610221955-50774cd97099; azure-identity 1.16.1; com.azure:azure-identity 1.12.2; 3 more packages under Affected packages), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm @azure/msal-node
- Affected
- >= 2.7.0, < 2.9.2
- Fixed in
- 2.9.2
NuGet microsoft.identity.client
- Affected
- >= 4.49.1, < 4.60.4>= 4.61.0, < 4.61.3
- Fixed in
- 4.61.3, 4.60.4
Go github.com/Azure/azure-sdk-for-go/sdk/azidentity
- Affected
- < 1.6.0-beta.4.0.20240610221955-50774cd97099
- Fixed in
- 1.6.0-beta.4.0.20240610221955-50774cd97099
PyPI azure-identity
- Affected
- < 1.16.1
- Fixed in
- 1.16.1
Maven com.azure:azure-identity
- Affected
- < 1.12.2
- Fixed in
- 1.12.2
npm @azure/identity
- Affected
- < 4.2.1
- Fixed in
- 4.2.1
NuGet azure.identity
- Affected
- < 1.11.4
- Fixed in
- 1.11.4
Maven com.microsoft.azure:msal4j
- Affected
- >= 1.14.4-beta, < 1.15.1
- Fixed in
- 1.15.1
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-m5vv-6r4h-3vj9 lists affected ranges: PyPI azure-identity >=0 =0 =0 =2.7.0 =4.49.1 =4.61.0 =0 =1.14.4-beta <1.15.1 (fixed); NuGet…
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-m5vv-6r4h-3vj9 lists affected ranges: PyPI azure-identity >=0 =0 =0 =0 =2.7.0 =1.14.4-beta =4.49.1 =4.61.0 =0 <1.6.0-beta.4.0.20240610221955-50774cd97099
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- 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 · score source
- EPSS
- CVE-2024-35255: 0.83% estimated exploitation activity in the next 30 days; percentile 57.60 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Azure Identity Libraries and Microsoft Authentication Library Elevation of Privilege Vulnerability.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-m5vv-6r4h-3vj9
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-m5vv-6r4h-3vj9
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2024-35255 Advisory: Azure Identity Libraries and Microsoft Authentication Library Elevation of Privilege Vulnerability IDs: CVE-2024-35255, GHSA-m5vv-6r4h-3vj9 Record: https://patchnext.com/advisories/cve-2024-35255 (revision 3, source checked 26 Oct 2026, 12:37 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: @azure/msal-node 2.9.2; microsoft.identity.client 4.61.3, 4.60.4; github.com/Azure/azure-sdk-for-go/sdk/azidentity 1.6.0-beta.4.0.20240610221955-50774cd97099; azure-identity 1.16.1; com.azure:azure-identity 1.12.2; @azure/identity 4.2.1; azure.identity 1.11.4; com.microsoft.azure:msal4j 1.15.1. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @azure/msal-node: affected >= 2.7.0, < 2.9.2; fixed in 2.9.2 - NuGet microsoft.identity.client: affected >= 4.49.1, < 4.60.4; >= 4.61.0, < 4.61.3; fixed in 4.61.3, 4.60.4 - Go github.com/Azure/azure-sdk-for-go/sdk/azidentity: affected < 1.6.0-beta.4.0.20240610221955-50774cd97099; fixed in 1.6.0-beta.4.0.20240610221955-50774cd97099 - PyPI azure-identity: affected < 1.16.1; fixed in 1.16.1 - Maven com.azure:azure-identity: affected < 1.12.2; fixed in 1.12.2 - npm @azure/identity: affected < 4.2.1; fixed in 4.2.1 - NuGet azure.identity: affected < 1.11.4; fixed in 1.11.4 - Maven com.microsoft.azure:msal4j: affected >= 1.14.4-beta, < 1.15.1; fixed in 1.15.1 ## Suggested inspection (read-only) - `npm ls @azure/msal-node --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. - NuGet microsoft.identity.client: check the installed version with your package manager. - Go github.com/Azure/azure-sdk-for-go/sdk/azidentity: check the installed version with your package manager. - `python -m pip show azure-identity`: prints the installed version. Run with the environment that serves production active. - Maven com.azure:azure-identity: check the installed version with your package manager. - `npm ls @azure/identity --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. - NuGet azure.identity: check the installed version with your package manager. - Maven com.microsoft.azure:msal4j: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @azure/msal-node, microsoft.identity.client, github.com/Azure/azure-sdk-for-go/sdk/azidentity, azure-identity, com.azure:azure-identity, @azure/identity, azure.identity, com.microsoft.azure:msal4j. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-m5vv-6r4h-3vj9 (OSV record GHSA-m5vv-6r4h-3vj9 lists affected ranges: PyPI azure-identity >=0 =0 =0 =2.7.0 =4.49.1 =4.61.0 =0 =1.14.4-beta <1.15.1 (fixed); NuGet…) - Verified: https://github.com/advisories/GHSA-m5vv-6r4h-3vj9 (GitHub-reviewed advisory GHSA-m5vv-6r4h-3vj9 lists affected ranges: PyPI azure-identity >=0 =0 =0 =0 =2.7.0 =1.14.4-beta =4.49.1 =4.61.0 =0 <1.6.0-beta.4.0.20240610221955-50774cd97099) Commands are suggestions: review each one before running it.
Loading voting…