Skip to content
Fencer Vulns
medium 5.3

CVE-2022-23551 json

AAD Pod Identity obtaining token with backslash

published 2022-12-21 3 y ago modified 2026-06-17 4 mo ago also GHSA-p82q-rxpm-hjpc , GO-2022-1181 , EUVD-2022-7701

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/Azure/aad-pod-identity 1.8.13
  • microsoft azure_ad_pod_identity 1.8.13
  • nmi CBL-Mariner 2.0 1.8.17-1

azure linux advisories AZL-34277

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-23551 updated cvss 5.3

aad-pod-identity: authentication bypass via backslash

  • Red Hat OpenShift Container Platform 4 openshift4/ose-hypershift-rhel8, openshift4/ose-cluster-capi-rhel8-operator, openshift4/ose-azure-cluster-api-controllers-rhel8
    affected: no fix available, no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

0.76% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L
NVD 3.1 5.3 CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L
GitHub 3.1 5.3 CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L

Affected packages

ecosystem package affected fixed in
go github.com/Azure/aad-pod-identity
<1.8.13
1.8.13

Affected products

  • Azure aad-pod-identity

Classification

Weakness
  • CWE-1259 Improper Restriction of Security Token Assignment
  • CWE-863 Incorrect Authorization

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.