aad-pod-identity assigns Azure Active Directory identities to Kubernetes applications and has now been deprecated as of 24 October 2022. 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. This issue has been fixed and has been included in AAD Pod Identity release version 1.8.13. If using the AKS pod-managed identities add-on, no action is required. The clusters should now be running the version 1.8.13 release.
References
Link | Resource |
---|---|
https://github.com/Azure/aad-pod-identity/commit/7e01970391bde6c360d077066ca17d059204cb5d | Patch Third Party Advisory |
https://github.com/Azure/aad-pod-identity/releases/tag/v1.8.13 | Third Party Advisory |
https://github.com/Azure/aad-pod-identity/security/advisories/GHSA-p82q-rxpm-hjpc | Third Party Advisory |
Configurations
History
No history.
Information
Published : 2022-12-21 20:15
Updated : 2023-01-04 19:54
NVD link : CVE-2022-23551
Mitre link : CVE-2022-23551
CVE.ORG link : CVE-2022-23551
JSON object : View
Products Affected
microsoft
- azure_ad_pod_identity
CWE
NVD-CWE-noinfo
CWE-1259
Improper Restriction of Security Token Assignment
CWE-863Incorrect Authorization