{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-21638 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-21638 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-21638 is a critical authentication bypass vulnerability in Azure ipam, published on 10 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-21638 and fix it if it is affected.\n\nWhat it is: CVE-2024-21638 is a critical authentication bypass vulnerability in Azure ipam, published on 10 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-21638 in the wild and no public exploit code.\n\nAffected product: Azure ipam. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-21638/ (Markdown: https://insights.sbomify.com/CVE-2024-21638/index.md)","id":"CVE-2024-21638","markdown":"https://insights.sbomify.com/CVE-2024-21638/index.md","name":"CVE-2024-21638","record":{"aliases":["GHSA-m8mp-jq4c-g8j6"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Azure IPAM solution","requires_auth":"none","summary":"Attackers can impersonate privileged users to access Azure data due to missing token validation in the IPAM solution.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"azure_ipam","vendor":"microsoft"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"},{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Azure IPAM solution Elevation of Privilege Vulnerability","id":"CVE-2024-21638","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"OOB Access in CefLayeredWindowUpdaterOSR::OnAllocatedSharedMemory","id":"CVE-2024-21639"},"packages":[],"prev":{"headline":"XSS in Authentik via JavaScript-URI as Redirect URI and form_post Response Mode","id":"CVE-2024-21637"},"products":["ipam"],"published":"2024-01-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-06-03","vendors":["Azure"]},"summary":"Attackers can impersonate privileged users to access Azure data due to missing token validation in the IPAM solution.","url":"https://insights.sbomify.com/CVE-2024-21638/"}