{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-39143 exists.","fix":"No fix has been published for CVE-2021-39143 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-39143 is a medium-severity path traversal vulnerability in spinnaker, published on 4 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-39143 and fix it if it is affected.\n\nWhat it is: CVE-2021-39143 is a medium-severity path traversal vulnerability in spinnaker, published on 4 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-39143 exists.\n\nAffected product: spinnaker. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2021-39143/ (Markdown: https://insights.sbomify.com/CVE-2021-39143/index.md)","id":"CVE-2021-39143","markdown":"https://insights.sbomify.com/CVE-2021-39143/index.md","name":"CVE-2021-39143","record":{"aliases":[],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Spinnaker continuous delivery","requires_auth":"low_privilege","summary":"Attackers can exploit path traversal in TAR file extraction during AppEngine deployments to overwrite system files, potentially enabling man-in-the-middle attacks.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"spinnaker","vendor":"linuxfoundation"}],"cvss":{"score":6.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Spinnaker is an open source, multi-cloud continuous delivery platform. A path traversal vulnerability was discovered in uses of TAR files by AppEngine for deployments. This uses a utility to extract files locally for deployment without validating the paths in that deployment don't override system files. This would allow an attacker to override files on the container, POTENTIALLY introducing a MITM type attack vector by replacing libraries or injecting wrapper files. Users are advised to update as soon as possible. For users unable to update disable Google AppEngine deployments and/or disable artifacts that provide TARs.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Path Traversal in spinnaker","id":"CVE-2021-39143","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"XStream Remote Code Execution","id":"CVE-2021-39144"},"packages":[],"prev":{"headline":"XStream is vulnerable to an Arbitrary Code Execution attack","id":"CVE-2021-39141"},"products":["spinnaker"],"published":"2022-01-04","related":[{"cvss_score":10,"headline":"Spinnaker: RCE when using gitrepo artifact types due to improper sanitization of user input on branch and paths","id":"CVE-2026-32604","kev_date_added":null,"published":"2026-04-20"},{"cvss_score":10,"headline":"Spinnaker vulnerable to RCE via expression parsing due to unrestricted context handling","id":"CVE-2026-32613","kev_date_added":null,"published":"2026-04-20"},{"cvss_score":10,"headline":"Improper Access Control in spinnaker","id":"CVE-2021-43832","kev_date_added":null,"published":"2022-01-04"},{"cvss_score":8.8,"headline":"Spinnaker: Non-safe yaml deserialization allowing RCE when using specific types","id":"CVE-2026-44795","kev_date_added":null,"published":"2026-07-10"},{"cvss_score":8.8,"headline":"Code injection in Netflix Spinnaker","id":"CVE-2020-9301","kev_date_added":null,"published":"2020-12-11"},{"cvss_score":7.9,"headline":"Spinnaker vulnerable to SSRF due to improper restrictions on http from user input","id":"CVE-2025-61916","kev_date_added":null,"published":"2026-01-05"},{"cvss_score":7.5,"headline":"Spinnaker: Improper yaml processing on kustomize bake operations","id":"CVE-2026-55175","kev_date_added":null,"published":"2026-07-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["spinnaker"]},"summary":"Attackers can exploit path traversal in TAR file extraction during AppEngine deployments to overwrite system files, potentially enabling man-in-the-middle attacks.","url":"https://insights.sbomify.com/CVE-2021-39143/"}