{"answers":{"affected":"1 open source package ship an affected version, including backoff.","exploited":"There is no known exploitation of RUSTSEC-2025-0012 in the wild and no public exploit code.","fix":"No fix has been published for RUSTSEC-2025-0012 yet. Limit exposure of the affected software until one is available.","what":"RUSTSEC-2025-0012 is a vulnerability in backoff, published on 4 Mar 2025."},"fix_prompt":"Check this codebase for RUSTSEC-2025-0012 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2025-0012 is a vulnerability in backoff, published on 4 Mar 2025. \nExploitation: There is no known exploitation of RUSTSEC-2025-0012 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- backoff (crates.io): affected from 0.0.0-0; no fix listed\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/RUSTSEC-2025-0012/ (Markdown: https://insights.sbomify.com/RUSTSEC-2025-0012/index.md)","id":"RUSTSEC-2025-0012","markdown":"https://insights.sbomify.com/RUSTSEC-2025-0012/index.md","name":"RUSTSEC-2025-0012","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["other"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust backoff library","requires_auth":"unknown","summary":"The backoff crate is unmaintained, posing supply chain risks; developers should migrate to the backon crate.","user_interaction":"unknown","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The [backoff](https://crates.io/crates/backoff) crate is no longer actively maintained. For exponential backoffs/retrying, you can use the [backon](https://crates.io/crates/backon) crate.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"`backoff` is unmaintained.","id":"RUSTSEC-2025-0012","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"supply_chain","year":"2025"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"backoff","purl":"pkg:cargo/backoff","source":"RUSTSEC-2025-0012"}],"products":null,"published":"2025-03-04","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"The backoff crate is unmaintained, posing supply chain risks; developers should migrate to the backon crate.","url":"https://insights.sbomify.com/RUSTSEC-2025-0012/"}