{"answers":{"affected":"2 open source packages ship an affected version, including tough. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41150 in the wild and no public exploit code.","fix":"Upgrade tough to 0.12.0 or later.","what":"CVE-2021-41150 is a high-severity path traversal vulnerability in awslabs tough, published on 19 Oct 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-41150 and fix it if it is affected.\n\nWhat it is: CVE-2021-41150 is a high-severity path traversal vulnerability in awslabs tough, published on 19 Oct 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-41150 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tough (crates.io): affected all versions; fixed in 0.12.0\n- tough (crates.io): affected all versions; fixed in 0.12.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-2021-41150/ (Markdown: https://insights.sbomify.com/CVE-2021-41150/index.md)","id":"CVE-2021-41150","markdown":"https://insights.sbomify.com/CVE-2021-41150/index.md","name":"CVE-2021-41150","record":{"aliases":["GHSA-r56q-vv3c-6g9c"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust TUF library","requires_auth":"low_privilege","summary":"Attackers can overwrite arbitrary JSON files on the system by exploiting improper sanitization of delegated role names in the tough library.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"tough","vendor":"amazon"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/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":"Tough provides a set of Rust libraries and tools for using and generating the update framework (TUF) repositories. The tough library, prior to 0.12.0, does not properly sanitize delegated role names when caching a repository, or when loading a repository from the filesystem. When the repository is cached or loaded, files ending with the .json extension could be overwritten with role metadata anywhere on the system. A fix is available in version 0.12.0. No workarounds to this issue are known.","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":"Improper sanitization of delegated role names in tough","id":"CVE-2021-41150","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"path_traversal","year":"2021"},"n_packages":2,"n_references":3,"next":{"headline":"Path Traversal in @backstage/plugin-scaffolder-backend","id":"CVE-2021-41151"},"packages":[{"ecosystem":"crates.io","fixed":["0.12.0"],"introduced":["0"],"last_affected":[],"package":"tough","purl":null,"source":"GHSA-r56q-vv3c-6g9c"},{"ecosystem":"crates.io","fixed":["0.12.0"],"introduced":["0"],"last_affected":[],"package":"tough","purl":"pkg:cargo/tough","source":"GHSA-r56q-vv3c-6g9c"}],"prev":{"headline":"Improper sanitization of target names in tough","id":"CVE-2021-41149"},"products":["tough"],"published":"2021-10-19","related":[{"cvss_score":8.6,"headline":"Improper verification of signature threshold in tough","id":"CVE-2020-15093","kev_date_added":null,"published":"2020-07-09"},{"cvss_score":8.2,"headline":"Improper sanitization of target names in tough","id":"CVE-2021-41149","kev_date_added":null,"published":"2021-10-19"},{"cvss_score":7.1,"headline":"Missing Delegated Metadata Validation in awslabs/tough","id":"CVE-2026-6967","kev_date_added":null,"published":"2026-04-24"},{"cvss_score":7.1,"headline":"Multiple Path Traversal Variants in awslabs/tough","id":"CVE-2026-6968","kev_date_added":null,"published":"2026-04-24"},{"cvss_score":7,"headline":"Signature Threshold Bypass in awslabs/tough Delegated Roles","id":"CVE-2026-6966","kev_date_added":null,"published":"2026-04-24"},{"cvss_score":5.7,"headline":"Root metadata version not validated in tough","id":"CVE-2025-2885","kev_date_added":null,"published":"2025-03-27"}],"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":["awslabs"]},"summary":"Attackers can overwrite arbitrary JSON files on the system by exploiting improper sanitization of delegated role names in the tough library.","url":"https://insights.sbomify.com/CVE-2021-41150/"}