CVE-2024-21638 json
Azure IPAM solution Elevation of Privilege Vulnerability
published 2024-01-10 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-19276
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
Azure IPAM (IP Address Management) is a lightweight solution developed on top of the Azure platform designed to help Azure customers manage their IP Address space easily and effectively. By design there is no write access to customers' Azure environments as the Service Principal used is only assigned the Reader role at the root Management Group level. Until recently, the solution lacked the validation of the passed in authentication token which may result in attacker impersonating any privileged user to access data stored within the IPAM instance and subsequently from Azure, causing an elevation of privilege. This vulnerability has been patched in version 3.0.0.
Patch / fix
- microsoft azure_ipam 3.0.0
- github.com/Azure/ipam@64ef2d0 commit
- github.com/Azure/ipam#218 pull request
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 18 mo ago
Exploit prediction
1.66% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Azure ipam
Classification
References
-
github.com
/Azure/ipam/pull/218
patch
-
github.com
/Azure/ipam/commit/64ef2d07edf16ffa50f29c7e0e25d32d974b367f
patch
-
github.com
/Azure/ipam/security/advisories/GHSA-m8mp-jq4c-g8j6
mitigation, vendor-advisory
Sources
- CVE List CVE-2024-21638
- NVD CVE-2024-21638
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.