Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go Maven📦 npm.NET NuGet🐍 PyPI

CVE-2024-35255

MEDIUM

Azure Identity Libraries and Microsoft Authentication Library Elevation of Privilege Vulnerability

Also known asGHSA-m5vv-6r4h-3vj9GO-2024-2918
Published
Jun 11, 2024
Updated
Jun 9, 2026
Affected
9 pkgs
Patched
9 / 9
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk51th percentile+0.56%
0.00%0.43%0.85%1.28%0.2%0.8%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

9 pkgs affected
🐹github.com/Azure/azure-sdk-for-go/sdk/azidentitycom.azure:azure-identitycom.microsoft.azure:msal4j📦@azure/identity📦@azure/msal-node.NETMicrosoft.Identity.Client.NETAzure.Identity.NETMicrosoft.Identity.Client+1 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go, Maven packages — download data is not available via public APIs for these ecosystems.

Description

Azure Identity Libraries and Microsoft Authentication Library Elevation of Privilege Vulnerability

Affected Packages

9 total 9 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/Azure/azure-sdk-for-go/sdk/azidentityall versions1.6.0-beta.4.0.20240610221955-50774cd97099
Mavencom.azure:azure-identityall versions1.12.2
Mavencom.microsoft.azure:msal4j1.14.4-beta&&< 1.15.11.15.1
📦npm@azure/identityall versions4.2.1
📦npm@azure/msal-node2.7.0&&< 2.9.22.9.2
.NETNuGetMicrosoft.Identity.Client4.49.1&&< 4.60.44.60.4

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/Azure/azure-sdk-for-go/sdk/azidentity. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/Azure/azure-sdk-for-go/sdk/azidentity to 1.6.0-beta.4.0.20240610221955-50774cd97099 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-35255 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2024-35255 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2024-35255. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Azure Identity Libraries and Microsoft Authentication Library Elevation of Privilege Vulnerability
O3 Security · Impact-Aware SCA

Is CVE-2024-35255 in your dependencies?

O3 detects CVE-2024-35255 across Go, Maven, npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.