CVE-2022-23551
AAD Pod Identity obtaining token with backslash
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.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- High
- User interaction
- Required
What an attacker can affect
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
Exploit likelihood
What each source reports
CVE List Score used
5.3
AAD Pod Identity obtaining token with backslash
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.
- Record
CVE-2022-23551- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L - Weakness
- CWE-1259, CWE-863
- Updated
- 2026-11-02
EUVDEUVD-2022-7701
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.
- Record
EUVD-2022-7701- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-p82q-rxpm-hjpc
5.3
AAD Pod Identity obtaining token with backslash
Impact
What kind of vulnerability is it? Who is impacted?
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.
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
- If using the AKS pod-managed identities add-on, no action is required. The clusters should now be running the
v1.8.13release.
For more information
If you have any questions or comments about this advisory:
Open an issue in Azure/aad-pod-identity
- Record
GHSA-p82q-rxpm-hjpc- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L - Weakness
- CWE-863
- Updated
- 2026-11-02
NVD
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.
- Record
CVE-2022-23551- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L - Weakness
- CWE-863, CWE-1259
- Updated
- 2026-11-02
OSVAZL-34277
5.3
CVE-2022-23551 affecting package nmi for versions less than 1.8.17-1
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.
- Record
AZL-34277- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L - Updated
- 2026-11-02
OSV
5.3
AAD Pod Identity obtaining token with backslash
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.
- Record
CVE-2022-23551- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L - Weakness
- CWE-1259, CWE-863
- Updated
- 2026-11-02
OSVGHSA-p82q-rxpm-hjpc
5.3
AAD Pod Identity obtaining token with backslash
Impact
What kind of vulnerability is it? Who is impacted?
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.
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
- If using the AKS pod-managed identities add-on, no action is required. The clusters should now be running the
v1.8.13release.
For more information
If you have any questions or comments about this advisory:
Open an issue in Azure/aad-pod-identity
- Record
GHSA-p82q-rxpm-hjpc- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L - Weakness
- CWE-863
- Updated
- 2026-11-02
OSVGO-2022-1181 No score
AAD Pod Identity obtaining token with backslash in github.com/Azure/aad-pod-identity
AAD Pod Identity obtaining token with backslash in github.com/Azure/aad-pod-identity
- Record
GO-2022-1181- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/Azure/aad-pod-identityGo |
before 1.8.13 | 1.8.13 |
nmiAzure Linux:2 |
before 1.8.17-1 | 1.8.17-1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2022-23551 is a medium vulnerability (CVSS 5.3) in Azure Aad-pod-identity, published December 21, 2022. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.76%, the 55th percentile. Fixed in github.com/Azure/aad-pod-identity 1.8.13.
References
github.com/Azure/aad-pod-identity/security/advisories/GHSA-p82q-rxpm-hjpc
github.com/Azure/aad-pod-identity/commit/7e01970391bde6c360d077066ca17d059204cb5d
github.com/Azure/aad-pod-identity/releases/tag/v1.8.13
nvd.nist.gov/vuln/detail/CVE-2022-23551
github.com/advisories/GHSA-p82q-rxpm-hjpc
github.com/CVEProject/cvelistV5/tree/main/cves/2022/23xxx/CVE-2022-23551.json
github.com/Azure/aad-pod-identity