{"answers":{"affected":"4 open source packages ship an affected version, including cargo. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-36113 in the wild and no public exploit code.","fix":"Upgrade cargo to a fixed version for your release line: 0.65.0 or 0.67.0.","what":"CVE-2022-36113 is a medium-severity path traversal vulnerability in rust-lang cargo, published on 14 Sep 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-36113 and fix it if it is affected.\n\nWhat it is: CVE-2022-36113 is a medium-severity path traversal vulnerability in rust-lang cargo, published on 14 Sep 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-36113 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- cargo (crates.io): affected all versions; fixed in 0.65.0\n- cargo (crates.io): affected all versions; fixed in 0.65.0\n- cargo (crates.io): affected from 0.66.0; fixed in 0.67.0\n- cargo (crates.io): affected from 0.66.0; fixed in 0.67.0\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-36113/ (Markdown: https://insights.sbomify.com/CVE-2022-36113/index.md)","id":"CVE-2022-36113","markdown":"https://insights.sbomify.com/CVE-2022-36113/index.md","name":"CVE-2022-36113","record":{"aliases":["DEBIAN-CVE-2022-36113","GHSA-rfj2-q3h3-hm5j","UBUNTU-CVE-2022-36113"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust package manager","requires_auth":"low_privilege","summary":"A malicious Rust crate can corrupt arbitrary files on the developer's machine via symlink handling during package extraction.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cargo","vendor":"rust-lang"}],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Cargo is a package manager for the rust programming language. After a package is downloaded, Cargo extracts its source code in the ~/.cargo folder on disk, making it available to the Rust projects it builds. To record when an extraction is successful, Cargo writes \"ok\" to the .cargo-ok file at the root of the extracted source code once it extracted all the files. It was discovered that Cargo allowed packages to contain a .cargo-ok symbolic link, which Cargo would extract. Then, when Cargo attempted to write \"ok\" into .cargo-ok, it would actually replace the first two bytes of the file the symlink pointed to with ok. This would allow an attacker to corrupt one file on the machine using Cargo to extract the package. Note that by design Cargo allows code execution at build time, due to build scripts and procedural macros. The vulnerabilities in this advisory allow performing a subset of the possible damage in a harder to track down way. Your dependencies must still be trusted if you want to be protected from attacks, as it's possible to perform the same attacks with build scripts and procedural macros. The vulnerability is present in all versions of Cargo. Rust 1.64, to be released on September 22nd, will include a fix for it. Since the vulnerability is just a more limited way to accomplish what a malicious build scripts or procedural macros can do, we decided not to publish Rust point releases backporting the security fix. Patch files are available for Rust 1.63.0 are available in the wg-security-response repository for people building their own toolchain.\nMitigations We recommend users of alternate registries to exercise care in which package they download, by only including trusted dependencies in their projects. Please note that even with these vulnerabilities fixed, by design Cargo allows arbitrary code execution at build time thanks to build scripts and procedural macros: a malicious dependency will be able to cause damage regardless of these vulnerabilities. crates.io implemented server-side checks to reject these kinds of packages years ago, and there are no packages on crates.io exploiting these vulnerabilities. crates.io users still need to exercise care in choosing their dependencies though, as remote code execution is allowed by design there as well.","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":"Extracting malicious crates can corrupt arbitrary files","id":"CVE-2022-36113","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"path_traversal","year":"2022"},"n_packages":4,"n_references":2,"next":{"headline":"Extracting malicious crates can fill the file system","id":"CVE-2022-36114"},"packages":[{"ecosystem":"crates.io","fixed":["0.65.0"],"introduced":["0"],"last_affected":[],"package":"cargo","purl":null,"source":"GHSA-rfj2-q3h3-hm5j"},{"ecosystem":"crates.io","fixed":["0.65.0"],"introduced":["0"],"last_affected":[],"package":"cargo","purl":"pkg:cargo/cargo","source":"GHSA-rfj2-q3h3-hm5j"},{"ecosystem":"crates.io","fixed":["0.67.0"],"introduced":["0.66.0"],"last_affected":[],"package":"cargo","purl":null,"source":"GHSA-rfj2-q3h3-hm5j"},{"ecosystem":"crates.io","fixed":["0.67.0"],"introduced":["0.66.0"],"last_affected":[],"package":"cargo","purl":"pkg:cargo/cargo","source":"GHSA-rfj2-q3h3-hm5j"}],"prev":{"headline":"Blind Server-Side Request Forgery (SSRF) in GLPI","id":"CVE-2022-36112"},"products":["cargo"],"published":"2022-09-14","related":[{"cvss_score":6.5,"headline":"Crates in third party registries can override the cached source of other crates","id":"CVE-2026-5223","kev_date_added":null,"published":"2026-05-25"},{"cvss_score":5.3,"headline":"Cargo did not verify SSH host keys","id":"CVE-2022-46176","kev_date_added":null,"published":"2023-01-11"},{"cvss_score":4.8,"headline":"Extracting malicious crates can fill the file system","id":"CVE-2022-36114","kev_date_added":null,"published":"2022-09-14"},{"cvss_score":2.3,"headline":"Cargo can be coerced to share credentials between registries","id":"CVE-2026-5222","kev_date_added":null,"published":"2026-05-25"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["rust-lang"]},"summary":"A malicious Rust crate can corrupt arbitrary files on the developer's machine via symlink handling during package extraction.","url":"https://insights.sbomify.com/CVE-2022-36113/"}