{"answers":{"affected":"2 open source packages ship an affected version, including tough. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-2887 in the wild and no public exploit code.","fix":"Upgrade tough to 0.20.0 or later.","what":"CVE-2025-2887 is a medium-severity vulnerability in AWS tough, published on 27 Mar 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-2887 and fix it if it is affected.\n\nWhat it is: CVE-2025-2887 is a medium-severity vulnerability in AWS tough, published on 27 Mar 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-2887 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tough (crates.io): affected all versions; fixed in 0.20.0\n- tough (crates.io): affected all versions; fixed in 0.20.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-2025-2887/ (Markdown: https://insights.sbomify.com/CVE-2025-2887/index.md)","id":"CVE-2025-2887","markdown":"https://insights.sbomify.com/CVE-2025-2887/index.md","name":"CVE-2025-2887","record":{"aliases":["GHSA-q6r9-r9pw-4cf7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust TUF library","requires_auth":"high_privilege","summary":"Attackers can alter target contents by exploiting a failure to detect delegated target rollbacks in the tough library.","user_interaction":"required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMZN","cpe":[{"product":"tough","vendor":"amazon"}],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-1025","name":"Comparison Using Wrong Factors"}],"description":"During a target rollback, the client fails to detect the rollback for delegated targets. This could cause the client to fetch a target from an incorrect source, altering the target contents. Users should upgrade to tough version 0.20.0 or later and ensure any forked or derivative code is patched to incorporate the new fixes.","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":"Failure to detect delegated target rollback in tough","id":"CVE-2025-2887","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"supply_chain","year":"2025"},"n_packages":2,"n_references":3,"next":{"headline":"Improper timestamp caching during snapshot rollback in tough","id":"CVE-2025-2888"},"packages":[{"ecosystem":"crates.io","fixed":["0.20.0"],"introduced":["0"],"last_affected":[],"package":"tough","purl":null,"source":"GHSA-q6r9-r9pw-4cf7"},{"ecosystem":"crates.io","fixed":["0.20.0"],"introduced":["0"],"last_affected":[],"package":"tough","purl":"pkg:cargo/tough","source":"GHSA-q6r9-r9pw-4cf7"}],"prev":{"headline":"Terminating targets role delegations are not respected in tough","id":"CVE-2025-2886"},"products":["tough"],"published":"2025-03-27","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":8.2,"headline":"Improper sanitization of delegated role names in tough","id":"CVE-2021-41150","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-14","vendors":["AWS"]},"summary":"Attackers can alter target contents by exploiting a failure to detect delegated target rollbacks in the tough library.","url":"https://insights.sbomify.com/CVE-2025-2887/"}