CVE-2022-23551
low-risk
Published 2022-12-21
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.
Do I need to act?
-
0.78% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
5
CVSS 5.3/10
Medium
LOCAL
/ LOW complexity
Affected Products (1)
Azure Ad Pod Identity
Affected Vendors
References (6)
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-hjp...
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-hjp...
26
/ 100
low-risk
Severity
18/34 · Moderate
Exploitability
3/34 · Minimal
Exposure
5/34 · Minimal