RUSTSEC-2023-0020 const-cstr is Unmaintained
Unmaintained Rust crate allows memory corruption and panics via unsound CStr handling, requiring migration to alternative libraries.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is RUSTSEC-2023-0020?
RUSTSEC-2023-0020 is a memory corruption vulnerability in const-cstr, published on 12 Mar 2023.
Official description
Last release was about five years ago.
The maintainer(s) have been unreachable to respond to any issues that may or may not include security issues.
The repository is now archived and there is no security policy in place to contact the maintainer(s) otherwise.
No direct fork exist.
const-cstr is Unsound
The crate violates the safety contract of ffi::CStr::from_bytes_with_nul_unchecked used in ConstCStr::as_cstr
No interior nul bytes checking is done either by the constructor or the canonical macro to create the ConstCStr
const-cstr Panic
Additionally the crate may cause runtime panics if statically compiled and ran with any untrusted data that is not nul-terminated.
This is however unlikely but the the crate should not be used for untrusted data in context where panic may create a DoS vector.
Possible Alternatives
The below may or may not provide alternative(s)
Which versions are affected by RUSTSEC-2023-0020?
1 open source package ship an affected version, including const-cstr.
| Package | Affected | Fixed in |
|---|---|---|
const-cstr crates.io | From 0.0.0-0 | None |
How do I fix RUSTSEC-2023-0020?
No fix has been published for RUSTSEC-2023-0020 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is RUSTSEC-2023-0020 being exploited?
There is no known exploitation of RUSTSEC-2023-0020 in the wild and no public exploit code.