{"answers":{"affected":"3 open source packages ship an affected version, including github.com/Azure/aad-pod-identity. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-23551 in the wild and no public exploit code.","fix":"Upgrade github.com/Azure/aad-pod-identity to 1.8.13 or later.","what":"CVE-2022-23551 is a medium-severity vulnerability in Azure aad-pod-identity, published on 21 Dec 2022."},"fix_prompt":"Check this codebase for CVE-2022-23551 and fix it if it is affected.\n\nWhat it is: CVE-2022-23551 is a medium-severity vulnerability in Azure aad-pod-identity, published on 21 Dec 2022. \nExploitation: There is no known exploitation of CVE-2022-23551 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/Azure/aad-pod-identity (Go): affected all versions; fixed in 1.8.13\n- github.com/Azure/aad-pod-identity (Go): affected all versions; fixed in 1.8.13\n- github.com/Azure/aad-pod-identity (Go): affected all versions; fixed in 1.8.13\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-23551/ (Markdown: https://insights.sbomify.com/CVE-2022-23551/index.md)","id":"CVE-2022-23551","markdown":"https://insights.sbomify.com/CVE-2022-23551/index.md","name":"CVE-2022-23551","record":{"aliases":["AZL-34277","GHSA-p82q-rxpm-hjpc","GO-2022-1181"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[{"product":"azure_ad_pod_identity","vendor":"microsoft"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-1259","name":"Improper Restriction of Security Token Assignment"}],"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"AAD Pod Identity obtaining token with backslash","id":"CVE-2022-23551","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":null,"year":"2022"},"n_packages":3,"n_references":3,"next":{"headline":"Grafana stored XSS in FileUploader component","id":"CVE-2022-23552"},"packages":[{"ecosystem":"Go","fixed":["1.8.13"],"introduced":["0"],"last_affected":[],"package":"github.com/Azure/aad-pod-identity","purl":null,"source":"GHSA-p82q-rxpm-hjpc"},{"ecosystem":"Go","fixed":["1.8.13"],"introduced":["0"],"last_affected":[],"package":"github.com/Azure/aad-pod-identity","purl":"pkg:golang/github.com/Azure/aad-pod-identity","source":"GHSA-p82q-rxpm-hjpc"},{"ecosystem":"Go","fixed":["1.8.13"],"introduced":["0"],"last_affected":[],"package":"github.com/Azure/aad-pod-identity","purl":"pkg:golang/github.com/Azure/aad-pod-identity","source":"GO-2022-1181"}],"prev":{"headline":"Discourse vulnerable to bypass of post max_length using HTML comments","id":"CVE-2022-23549"},"products":["aad-pod-identity"],"published":"2022-12-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-15","vendors":["Azure"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2022-23551/"}