{"answers":{"affected":"1 open source package ship an affected version, including cve-rs.","exploited":"There is no known exploitation of RUSTSEC-2025-0028 in the wild and no public exploit code.","fix":"No fix has been published for RUSTSEC-2025-0028 yet. Limit exposure of the affected software until one is available.","what":"RUSTSEC-2025-0028 is a memory corruption vulnerability in cve-rs, published on 10 Feb 2025."},"fix_prompt":"Check this codebase for RUSTSEC-2025-0028 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2025-0028 is a memory corruption vulnerability in cve-rs, published on 10 Feb 2025. \nExploitation: There is no known exploitation of RUSTSEC-2025-0028 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- cve-rs (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-0028/ (Markdown: https://insights.sbomify.com/RUSTSEC-2025-0028/index.md)","id":"RUSTSEC-2025-0028","markdown":"https://insights.sbomify.com/RUSTSEC-2025-0028/index.md","name":"RUSTSEC-2025-0028","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust memory safety crate","requires_auth":"none","summary":"The cve-rs crate demonstrates memory vulnerabilities in safe Rust by exploiting a compiler soundness bug, potentially allowing code execution or crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This crate is a joke and should never be used.\n\n`cve-rs` provides demonstrations of common memory vulnerabilities (such as buffer overflows and segfaults) implemented completely within safe Rust.\n\nInternally, this crate does not use unsafe code, it instead exploits a soundness bug in rustc: https://github.com/rust-lang/rust/issues/25860","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":"cve-rs introduces memory vulnerabilities in safe Rust","id":"RUSTSEC-2025-0028","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"cve-rs","purl":"pkg:cargo/cve-rs","source":"RUSTSEC-2025-0028"}],"products":null,"published":"2025-02-10","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 cve-rs crate demonstrates memory vulnerabilities in safe Rust by exploiting a compiler soundness bug, potentially allowing code execution or crashes.","url":"https://insights.sbomify.com/RUSTSEC-2025-0028/"}