{"id":"CVE-2022-23551","aliases":["AZL-34277","EUVD-2022-7701","GHSA-p82q-rxpm-hjpc","GO-2022-1181"],"status":"published","title":"AAD Pod Identity obtaining token with backslash","description":"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.","severity":{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00763,"percentile":0.55812,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-1259","CWE-863"],"published":"2022-12-21T18:48:22Z","modified":"2026-10-28T02:31:07Z","fixes":[{"ecosystem":"Go","package":"github.com/Azure/aad-pod-identity","fixed_in":["1.8.13"],"sources":["ghsa","osv"]},{"ecosystem":"Azure Linux:2","package":"nmi","fixed_in":["1.8.17-1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"Go","package":"github.com/Azure/aad-pod-identity","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.8.13"}]}]},{"source":"osv","ecosystem":"Azure Linux:2","package":"nmi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.8.17-1"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/Azure/aad-pod-identity","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.8.13"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/Azure/aad-pod-identity","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.8.13"}]}]}],"products":[{"vendor":"azure","product":"aad-pod-identity"},{"vendor":"microsoft","product":"azure_ad_pod_identity"}],"references":[{"url":"https://github.com/Azure/aad-pod-identity/security/advisories/GHSA-p82q-rxpm-hjpc","tags":["x_refsource_CONFIRM","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://github.com/Azure/aad-pod-identity/commit/7e01970391bde6c360d077066ca17d059204cb5d","tags":["x_refsource_MISC","x_transferred","Patch","Third Party Advisory","fix","web"]},{"url":"https://github.com/Azure/aad-pod-identity/releases/tag/v1.8.13","tags":["x_refsource_MISC","x_transferred","Third Party Advisory","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-23551","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-p82q-rxpm-hjpc"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/23xxx/CVE-2022-23551.json","tags":["advisory"]},{"url":"https://github.com/Azure/aad-pod-identity","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2022-23551","title":"AAD Pod Identity obtaining token with backslash","description":"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.","status":"published","published":"2022-12-21T19:50:15.247Z","modified":"2025-04-15T18:10:15.229Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L","level":"medium","assessor":"cna"}],"cwes":["CWE-1259","CWE-863"],"updated_at":"2026-11-02T14:34:29.842547Z"}],"euvd":[{"id":"EUVD-2022-7701","description":"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.","status":"published","published":"2022-12-21T19:50:15Z","modified":"2025-04-15T18:10:15Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L","level":"medium"}],"updated_at":"2026-11-02T20:52:27.766207Z"}],"ghsa":[{"id":"GHSA-p82q-rxpm-hjpc","title":"AAD Pod Identity obtaining token with backslash","description":"### Impact\n_What kind of vulnerability is it? Who is impacted?_\nThe [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.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n- 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)\n- 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.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\nOpen an issue in [Azure/aad-pod-identity](https://github.com/Azure/aad-pod-identity)\n","status":"published","published":"2022-12-21T18:48:22Z","modified":"2023-01-30T05:01:03Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L","level":"medium"}],"cwes":["CWE-863"],"updated_at":"2026-11-02T14:36:27.500048Z"}],"nvd":[{"id":"CVE-2022-23551","description":"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.","status":"published","published":"2022-12-21T20:15:09.49Z","modified":"2026-06-17T04:30:20.38Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L","level":"medium","assessor":"secondary"},{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L","level":"medium","assessor":"primary"}],"cwes":["CWE-863","CWE-1259"],"updated_at":"2026-11-02T14:07:34.031641Z"}],"osv":[{"id":"AZL-34277","title":"CVE-2022-23551 affecting package nmi for versions less than 1.8.17-1","description":"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.","status":"published","published":"2022-12-21T20:15:09Z","modified":"2026-04-21T04:27:05.215913Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L","level":"medium"}],"updated_at":"2026-11-02T15:28:03.821827Z"},{"id":"CVE-2022-23551","title":"AAD Pod Identity obtaining token with backslash","description":"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.","status":"published","published":"2022-12-21T19:50:15.247Z","modified":"2026-10-28T02:31:07.512676995Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L","level":"medium"}],"cwes":["CWE-1259","CWE-863"],"updated_at":"2026-11-02T15:44:24.061177Z"},{"id":"GHSA-p82q-rxpm-hjpc","title":"AAD Pod Identity obtaining token with backslash","description":"### Impact\n_What kind of vulnerability is it? Who is impacted?_\nThe [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.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n- 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)\n- 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.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\nOpen an issue in [Azure/aad-pod-identity](https://github.com/Azure/aad-pod-identity)\n","status":"published","published":"2022-12-21T18:48:22Z","modified":"2024-08-21T16:28:54.895206Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L","level":"medium"}],"cwes":["CWE-863"],"updated_at":"2026-11-02T15:46:52.891208Z"},{"id":"GO-2022-1181","title":"AAD Pod Identity obtaining token with backslash in github.com/Azure/aad-pod-identity","description":"AAD Pod Identity obtaining token with backslash in github.com/Azure/aad-pod-identity","status":"published","published":"2024-08-21T16:03:59Z","modified":"2026-03-03T04:52:49.064298Z","updated_at":"2026-11-02T15:47:00.918515Z"}]}}