What is GHSA-p82q-rxpm-hjpc?

GHSA-p82q-rxpm-hjpc is a security advisory published by GitHub Security Advisories with Medium severity. AAD Pod Identity obtaining token with backslash

Which CVE IDs does GHSA-p82q-rxpm-hjpc cover?

GHSA-p82q-rxpm-hjpc covers the following CVE IDs: CVE-2022-23551. Each CVE has its own detail page on EchelonGraph Pulse with the synthesized EG score.

What is the CVSS v3 score of GHSA-p82q-rxpm-hjpc?

GHSA-p82q-rxpm-hjpc has a CVSS v3 base score of 5.3, published by GitHub Security Advisories.

Which products are affected by GHSA-p82q-rxpm-hjpc?

GHSA-p82q-rxpm-hjpc affects 1 product, including: go/github.com/Azure/aad-pod-identity:\u003c 1.8.13.

GHSA-p82q-rxpm-hjpcMediumCVSS 5.3

AAD Pod Identity obtaining token with backslash

Vendor

GitHub Security Advisories

Published

December 21, 2022

Last Modified

January 30, 2023

🔗 CVE IDs covered (1)

CVE-2022-23551 →

📋 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

🎯 Affected products1

go/github.com/Azure/aad-pod-identity:< 1.8.13