Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Go package

github.com/Azure/aad-pod-identity

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.3GoPublished

    AAD Pod Identity obtaining token with backslash

    CVE-2022-23551 · GHSA-p82q-rxpm-hjpc

    Affected
    • Go github.com/Azure/aad-pod-identity < 1.8.13
    Fixed in
    1.8.13· Vendor fix available
    Issue
    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

    Recommended action: Upgrade to 1.8.13 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →