CVE-2022-23551

mediumpriority · track · 21OT risk · elevatedEPSS 0.008 · 55 %ileEURUUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
0.76% (55th) EPSS
CVSS 5.3 · medium
Is it mine?
4 products
Check your exposure
Who says so?
5 sources
cnnvd · enisa_euvd · fstec_bdu · osv

EPSS · scored 2026-10-26

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.

01

cvss

Technical severity, 0–10. One row per scoring source.

5.3
010

base score 0–10 · higher = more severe · hover a vector to decode

v3.15.3mediumCVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:Lprimary · NVD / NIST USexploitability 0.6 · impact 4.7
v3.15.3mediumAV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:Lsecondary · FSTEC (BDU) RU
v3.15.3mediumCVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:Lsecondary · ENISA EU
v3.15.3mediumCVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:Lsecondary · security-advisories@github.comexploitability 0.6 · impact 4.7
v3.15.3mediumCVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:Lsecondary · OSV
v3.14.9mediumCVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L/E:Usecondary · CVSS-BT (t0sche)
02

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Trackcoordinatorcisa_ssvcUS
03

weaknesses

The CWE weakness classes this flaw belongs to.

04

affected products (4)

Products and version ranges known to be affected.

05

advisories (2)

Vendor and ecosystem advisories describing this.

  • GHSA-p82q-rxpm-hjpcAAD Pod Identity obtaining token with backslash2022-12-21ghsa · osvUS

    ### Impact _What kind of vulnerability is it? Who is impacted?_ The [NMI](https://azure.github.io/aad-pod-identity/docs/concepts/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](https://learn.microsoft.com/en-us/azure/virtual-machines/windows/instance-metadata-service?tabs=windows) 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](https://github.com/Azure/aad-pod-identity/releases/tag/v1.8.13) - If using the [AKS pod-managed identities add-on](https://learn.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity), no action is required. The clusters should now be running the `v1.8.13` release. ### For more information If you have any questions or comments about this advisory: Open an issue in [Azure/aad-pod-identity](https://github.com/Azure/aad-pod-identity)

  • GO-2022-1181AAD Pod Identity obtaining token with backslash in github.com/Azure/aad-pod-identity2024-08-21vendor · osvUS

    AAD Pod Identity obtaining token with backslash in github.com/Azure/aad-pod-identity

06

also known as (6)

Other names and identifiers for this entity.

07

sources

Which sources assert this record, and when.

published 2022-12-21modified 2026-06-17
08

references (10)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan