{"answers":{"affected":"1 open source package ship an affected version, including github.com/linkerd/linkerd2.","exploited":"There is no known exploitation of CVE-2024-40632 in the wild and no public exploit code.","fix":"Upgrade github.com/linkerd/linkerd2 to 0.5.1-0.20240614165515-35fb2d6d11ef or later.","what":"CVE-2024-40632 is a low-severity server-side request forgery vulnerability in linkerd2, published on 15 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-40632 and fix it if it is affected.\n\nWhat it is: CVE-2024-40632 is a low-severity server-side request forgery vulnerability in linkerd2, published on 15 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-40632 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/linkerd/linkerd2 (Go): affected all versions; fixed in 0.5.1-0.20240614165515-35fb2d6d11ef\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-2024-40632/ (Markdown: https://insights.sbomify.com/CVE-2024-40632/index.md)","id":"CVE-2024-40632","markdown":"https://insights.sbomify.com/CVE-2024-40632/index.md","name":"CVE-2024-40632","record":{"aliases":["GHSA-6v94-gj6x-jqj7","GO-2024-2984"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes service mesh","requires_auth":"none","summary":"An attacker can exploit SSRF in the application to trigger a denial-of-service attack on Linkerd by accessing its shutdown endpoint.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Linkerd is an open source, ultralight, security-first service mesh for Kubernetes. In affected versions when the application being run by linkerd is susceptible to SSRF, an attacker could potentially trigger a denial-of-service (DoS) attack by making requests to localhost:4191/shutdown. Linkerd could introduce an optional environment variable to control a token that must be passed as a header. Linkerd should reject shutdown requests that do not include this header. This issue has been addressed in release version edge-24.6.2 and all users are advised to upgrade. There are no known workarounds for this vulnerability.","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":"Linkerd potential access to the shutdown endpoint","id":"CVE-2024-40632","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"ssrf","year":"2024"},"n_packages":1,"n_references":3,"next":{"headline":"Customer data leak via adjustments API endpoint in Sylius","id":"CVE-2024-40633"},"packages":[{"ecosystem":"Go","fixed":["0.5.1-0.20240614165515-35fb2d6d11ef"],"introduced":["0"],"last_affected":[],"package":"github.com/linkerd/linkerd2","purl":"pkg:golang/github.com/linkerd/linkerd2","source":"GO-2024-2984"}],"prev":{"headline":"Cross-site Scripting (XSS) in media embed element when using custom URL parsers in plate media","id":"CVE-2024-40631"},"products":["linkerd2"],"published":"2024-07-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"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":"2024-08-02","vendors":["linkerd"]},"summary":"An attacker can exploit SSRF in the application to trigger a denial-of-service attack on Linkerd by accessing its shutdown endpoint.","url":"https://insights.sbomify.com/CVE-2024-40632/"}