{"answers":{"affected":"1 open source package ship an affected version, including claim.","exploited":"There is no known exploitation of RUSTSEC-2022-0077 in the wild and no public exploit code.","fix":"No fix has been published for RUSTSEC-2022-0077 yet. Limit exposure of the affected software until one is available.","what":"RUSTSEC-2022-0077 is a vulnerability in claim, published on 4 Dec 2022."},"fix_prompt":"Check this codebase for RUSTSEC-2022-0077 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2022-0077 is a vulnerability in claim, published on 4 Dec 2022. \nExploitation: There is no known exploitation of RUSTSEC-2022-0077 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- claim (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-2022-0077/ (Markdown: https://insights.sbomify.com/RUSTSEC-2022-0077/index.md)","id":"RUSTSEC-2022-0077","markdown":"https://insights.sbomify.com/RUSTSEC-2022-0077/index.md","name":"RUSTSEC-2022-0077","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["other"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust testing library","requires_auth":"unknown","summary":"The unmaintained Rust crate 'claim' poses supply chain risks due to lack of updates and dependency issues, requiring migration to alternatives.","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 last release was in February 2021, almost two years ago.\n\nThe maintainer has been unresponsive regarding this crate for over a year.\n\nA pending issue with `claim`'s dependencies has made the crate [difficult to use](https://github.com/svartalf/rust-claim/issues/9).\n\n## Possible Alternative(s)\n\nThe below list has not been vetted in any way and may or may not contain alternatives;\n\n- [`claims`](https://crates.io/crates/claims), a direct fork of the `claim` 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":"`claim` is Unmaintained","id":"RUSTSEC-2022-0077","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"supply_chain","year":"2022"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"claim","purl":"pkg:cargo/claim","source":"RUSTSEC-2022-0077"}],"products":null,"published":"2022-12-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 unmaintained Rust crate 'claim' poses supply chain risks due to lack of updates and dependency issues, requiring migration to alternatives.","url":"https://insights.sbomify.com/RUSTSEC-2022-0077/"}