AAD Pod Identity obtaining token with backslashGHSA-p82q-rxpm-hjpc
MEDIUMFix: Azure/aad-pod-identity@7e01970GHSA-p82q-rxpm-hjpc is a medium-severity (CVSS 5.3) CWE-863 vulnerability in github.com/Azure/aad-pod-identity. A fix is available for github.com/Azure/aad-pod-identity — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-p82q-rxpm-hjpc.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/Azure/aad-pod-identityReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
What kind of vulnerability is it? Who is impacted?
The NMI component in AAD Pod Identity intercepts and validates token requests based on regex. In this case, a token request made with backslash in the request (example: /metadata/identity\oauth2\token/) would bypass the NMI validation and be sent to IMDS allowing a pod in the cluster to access identities that it shouldn't have access to.
Patches
Has the problem been patched? What versions should users upgrade to?
- We analyzed this bug and determined that we needed to fix it. This fix has been included in AAD Pod Identity release v1.8.13
- If using the AKS pod-managed identities add-on, no action is required. The clusters should now be running the
v1.8.13release.
For more information
If you have any questions or comments about this advisory:
Open an issue in Azure/aad-pod-identity
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/Azure/aad-pod-identity | all versions | 1.8.13go get github.com/Azure/aad-pod-identity@v1.8.13 |
Affected Products
azure ad pod identitymicrosoftDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/Azure/aad-pod-identity, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/Azure/aad-pod-identity to 1.8.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p82q-rxpm-hjpc is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is GHSA-p82q-rxpm-hjpc in your dependencies?
Find it across Go, including transitive dependencies.