CVE-2022-23551
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.
Scoring
- Severity
- MEDIUM
- CVSS base score
- 5.3
- CVSS vector
- CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L
- EPSS probability
- 0.78%
- CWE
- CWE-1259, CWE-863
- Published
- 2022-12-21
- Last modified
- 2026-03-13
Affected products
- Azure aad-pod-identity
Weakness type
Related vulnerabilities
- CVE-2026-58429 — Public-Only Personal access tokens scope bypass in Organization and Permission Endpoints
- CVE-2026-54593 — Pterodactyl's improper JWT scoping allows subuser to upload files when not explicitly granted `file.create` permissions
- CVE-2026-25700 — Apache Answer: AdminToken not invalidated after admin deactivation
- CVE-2026-40264 — OpenBao's Token Store Allows Cross-Namespace Renewal, Revocation
- CVE-2024-45448 — Page table protection configuration vulnerability in the trusted firmware module...
- CVE-2024-41948 — biscuit-java vulnerable to public key confusion in third party block
- CVE-2024-36111 — KubePi's JWT token validation has a defect
- CVE-2022-23541 — jsonwebtoken's insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC