Aad Pod Identity
Approved changes feed: RSS · Atom
cpe:2.3:a:azure:aad-pod-identity:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Azure (bcdde641-20ca-55ac-abda-dda8306c0a74) |
|---|---|
| Product | Aad Pod Identity (1e733d73-8e0e-566c-a95b-bb5255f94c8d) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-23551 |
vulnerable | 2026-06-08 05:40:57.749743 |
AAD Pod Identity obtaining token with backslash
MEDIUM (5.3)
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.
Published: 2022-12-21T19:50:15.247Z
Updated: 2025-04-15T18:10:15.229Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.