Skip to content

AAD Pod Identity obtaining token with backslash

Moderate severity GitHub Reviewed Published Dec 21, 2022 in Azure/aad-pod-identity • Updated Jan 30, 2023

Package

gomod github.com/Azure/aad-pod-identity (Go)

Affected versions

< 1.8.13

Patched versions

1.8.13

Description

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.13 release.

For more information

If you have any questions or comments about this advisory:

Open an issue in Azure/aad-pod-identity

References

@aramase aramase published to Azure/aad-pod-identity Dec 21, 2022
Published to the GitHub Advisory Database Dec 21, 2022
Reviewed Dec 21, 2022
Published by the National Vulnerability Database Dec 21, 2022
Last updated Jan 30, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L

EPSS score

0.093%
(40th percentile)

Weaknesses

CVE ID

CVE-2022-23551

GHSA ID

GHSA-p82q-rxpm-hjpc

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.