{"answers":{"affected":"1 open source package ship an affected version, including const-cstr.","exploited":"There is no known exploitation of RUSTSEC-2023-0020 in the wild and no public exploit code.","fix":"No fix has been published for RUSTSEC-2023-0020 yet. Limit exposure of the affected software until one is available.","what":"RUSTSEC-2023-0020 is a memory corruption vulnerability in const-cstr, published on 12 Mar 2023."},"fix_prompt":"Check this codebase for RUSTSEC-2023-0020 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2023-0020 is a memory corruption vulnerability in const-cstr, published on 12 Mar 2023. \nExploitation: There is no known exploitation of RUSTSEC-2023-0020 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- const-cstr (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-2023-0020/ (Markdown: https://insights.sbomify.com/RUSTSEC-2023-0020/index.md)","id":"RUSTSEC-2023-0020","markdown":"https://insights.sbomify.com/RUSTSEC-2023-0020/index.md","name":"RUSTSEC-2023-0020","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 CStr library","requires_auth":"none","summary":"Unmaintained Rust crate allows memory corruption and panics via unsound CStr handling, requiring migration to alternative libraries.","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":"Last release was about five years ago.\n\nThe maintainer(s) have been unreachable to respond to any issues that may or may not include security issues.\n\nThe repository is now archived and there is no security policy in place to contact the maintainer(s) otherwise.\n\nNo direct fork exist.\n\n# const-cstr is Unsound\n\nThe crate violates the safety contract of [ffi::CStr::from_bytes_with_nul_unchecked](https://doc.rust-lang.org/std/ffi/struct.CStr.html#method.from_bytes_with_nul_unchecked) used in `ConstCStr::as_cstr`\n\nNo interior nul bytes checking is done either by the constructor or the canonical macro to create the `ConstCStr`\n\n# const-cstr Panic\n\nAdditionally the crate may cause runtime panics if statically compiled and ran with any untrusted data that is not nul-terminated.\n\nThis is however unlikely but the the crate should not be used for untrusted data in context where panic may create a DoS vector.\n\n## Possible Alternatives\n\nThe below may or may not provide alternative(s)\n\n- [const_str::cstr!](https://docs.rs/const-str/latest/const_str/macro.cstr.html)\n- [cstr::cstr!](https://crates.io/crates/cstr)","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":"const-cstr is Unmaintained","id":"RUSTSEC-2023-0020","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"const-cstr","purl":"pkg:cargo/const-cstr","source":"RUSTSEC-2023-0020"}],"products":null,"published":"2023-03-12","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":"Unmaintained Rust crate allows memory corruption and panics via unsound CStr handling, requiring migration to alternative libraries.","url":"https://insights.sbomify.com/RUSTSEC-2023-0020/"}