{"answers":{"affected":"6 open source packages ship an affected version, including tar. It affects 3 products.","exploited":"There is no known exploitation of CVE-2021-37713 in the wild and no public exploit code.","fix":"Upgrade tar to a fixed version for your release line: 4.4.18, 5.0.10 or 6.1.9.","what":"CVE-2021-37713 is a high-severity path traversal vulnerability in Oracle Graalvm, published on 31 Aug 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-37713 and fix it if it is affected.\n\nWhat it is: CVE-2021-37713 is a high-severity path traversal vulnerability in Oracle Graalvm, published on 31 Aug 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-37713 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tar (npm): affected all versions; fixed in 4.4.18\n- tar (npm): affected all versions; fixed in 4.4.18\n- tar (npm): affected from 5.0.0; fixed in 5.0.10\n- tar (npm): affected from 5.0.0; fixed in 5.0.10\n- tar (npm): affected from 6.0.0; fixed in 6.1.9\n- tar (npm): affected from 6.0.0; fixed in 6.1.9\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-37713/ (Markdown: https://insights.sbomify.com/CVE-2021-37713/index.md)","id":"CVE-2021-37713","markdown":"https://insights.sbomify.com/CVE-2021-37713/index.md","name":"CVE-2021-37713","record":{"aliases":["ALPINE-CVE-2021-37713","CLEANSTART-2026-BE95243","CLEANSTART-2026-BX59752","GHSA-5955-9wpr-37jh","ROOT-APP-NPM-CVE-2021-37713"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Node.js tar library","requires_auth":"none","summary":"Arbitrary file creation and code execution via path traversal on Windows in node-tar due to insufficient sanitization of drive-letter paths.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"tar","vendor":"npmjs"},{"product":"graalvm","vendor":"oracle"},{"product":"sinec_infrastructure_network_services","vendor":"siemens"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"The npm package \"tar\" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\\path`. If the drive letter does not match the extraction target, for example `D:\\extraction\\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory. Additionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path. This only affects users of `node-tar` on Windows systems. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.","ecosystems":["npm"],"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 Creation/Overwrite on Windows via insufficient relative path sanitization","id":"CVE-2021-37713","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"oracle:graalvm","products":["oracle:graalvm","siemens:sinec_infrastructure_network_services"],"type":"path_traversal","year":"2021"},"n_packages":6,"n_references":4,"next":{"headline":"Crafted input may cause the jsoup HTML and XML parser to get stuck, timeout, or throw unchecked exceptions","id":"CVE-2021-37714"},"packages":[{"ecosystem":"npm","fixed":["4.4.18"],"introduced":["0"],"last_affected":[],"package":"tar","purl":null,"source":"GHSA-5955-9wpr-37jh"},{"ecosystem":"npm","fixed":["4.4.18"],"introduced":["0"],"last_affected":[],"package":"tar","purl":"pkg:npm/tar","source":"GHSA-5955-9wpr-37jh"},{"ecosystem":"npm","fixed":["5.0.10"],"introduced":["5.0.0"],"last_affected":[],"package":"tar","purl":null,"source":"GHSA-5955-9wpr-37jh"},{"ecosystem":"npm","fixed":["5.0.10"],"introduced":["5.0.0"],"last_affected":[],"package":"tar","purl":"pkg:npm/tar","source":"GHSA-5955-9wpr-37jh"},{"ecosystem":"npm","fixed":["6.1.9"],"introduced":["6.0.0"],"last_affected":[],"package":"tar","purl":null,"source":"GHSA-5955-9wpr-37jh"},{"ecosystem":"npm","fixed":["6.1.9"],"introduced":["6.0.0"],"last_affected":[],"package":"tar","purl":"pkg:npm/tar","source":"GHSA-5955-9wpr-37jh"}],"prev":{"headline":"Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links","id":"CVE-2021-37712"},"products":["node-tar"],"published":"2021-08-31","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":"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-04","vendors":["npm"]},"summary":"Arbitrary file creation and code execution via path traversal on Windows in node-tar due to insufficient sanitization of drive-letter paths.","url":"https://insights.sbomify.com/CVE-2021-37713/"}