{"answers":{"affected":"3 open source packages ship an affected version, including tar. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20990 in the wild and no public exploit code.","fix":"Upgrade tar to 0.4.16 or later.","what":"CVE-2018-20990 is a high-severity path traversal vulnerability in n/a, published on 26 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-20990 and fix it if it is affected.\n\nWhat it is: CVE-2018-20990 is a high-severity path traversal vulnerability in n/a, published on 26 Aug 2019. 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-2018-20990 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tar (crates.io): affected all versions; fixed in 0.4.16\n- tar (crates.io): affected all versions; fixed in 0.4.16\n- tar (crates.io): affected from 0.0.0-0; fixed in 0.4.16\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-2018-20990/ (Markdown: https://insights.sbomify.com/CVE-2018-20990/index.md)","id":"CVE-2018-20990","markdown":"https://insights.sbomify.com/CVE-2018-20990/index.md","name":"CVE-2018-20990","record":{"aliases":["GHSA-2367-c296-3mp2","RUSTSEC-2018-0002","UBUNTU-CVE-2018-20990"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust tar crate","requires_auth":"none","summary":"Attackers can overwrite arbitrary files via malicious symlinks or hardlinks in TAR archives processed by the Rust tar crate.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tar","vendor":"tar_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"An issue was discovered in the tar crate before 0.4.16 for Rust. Arbitrary file overwrite can occur via a symlink or hardlink in a TAR archive.","ecosystems":["crates.io"],"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":"Arbitrary file overwrite in tar-rs","id":"CVE-2018-20990","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"path_traversal","year":"2018"},"n_packages":3,"n_references":1,"next":{"headline":"Double free in smallvec","id":"CVE-2018-20991"},"packages":[{"ecosystem":"crates.io","fixed":["0.4.16"],"introduced":["0"],"last_affected":[],"package":"tar","purl":null,"source":"GHSA-2367-c296-3mp2"},{"ecosystem":"crates.io","fixed":["0.4.16"],"introduced":["0"],"last_affected":[],"package":"tar","purl":"pkg:cargo/tar","source":"GHSA-2367-c296-3mp2"},{"ecosystem":"crates.io","fixed":["0.4.16"],"introduced":["0.0.0-0"],"last_affected":[],"package":"tar","purl":"pkg:cargo/tar","source":"RUSTSEC-2018-0002"}],"prev":{"headline":"Integer underflow in untrusted","id":"CVE-2018-20989"},"products":["n/a"],"published":"2019-08-26","related":[{"cvss_score":7.5,"headline":"Links in archive can create arbitrary directories","id":"CVE-2021-38511","kev_date_added":null,"published":"2021-08-10"},{"cvss_score":5.1,"headline":"tar-rs: unpack_in can chmod arbitrary directories by following symlinks","id":"CVE-2026-33056","kev_date_added":null,"published":"2026-03-20"}],"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":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can overwrite arbitrary files via malicious symlinks or hardlinks in TAR archives processed by the Rust tar crate.","url":"https://insights.sbomify.com/CVE-2018-20990/"}