rkyv
Affected
- introduced
0.0.0-0, fixed0.7.46, introduced0.8.0, fixed0.8.13(semver)
Fixed versions
0.7.46, 0.8.13
Fix
- Fixed version
0.7.46cargo update -p rkyv --precise 0.7.46 - Fixed version
0.8.13cargo update -p rkyv --precise 0.8.13
Advisory
Also known as: None
Potential Undefined Behaviors in Arc<T>/Rc<T> impls of from_value on OOM
The SharedPointer::alloc implementation for sync::Arc<T> and rc::Rc<T> in rkyv/src/impls/alloc/rc/atomic.rs (and rc.rs) does not check if the allocator returns a null pointer on OOM (Out of Memory).
This null pointer can flow through to SharedPointer::from_value, which calls Box::from_raw(ptr) with the null pointer. This triggers undefined behavior when utilizing safe deserialization APIs (such as rkyv::from_bytes or rkyv::deserialize_using) if an OOM condition occurs during the allocation of the shared pointer.
The issue is reachable through safe code and violates Rust's safety guarantees.
Not rated by the source.
0.0.0-0, fixed 0.7.46, introduced 0.8.0, fixed 0.8.13 (semver)0.7.46, 0.8.13
0.7.46cargo update -p rkyv --precise 0.7.460.8.13cargo update -p rkyv --precise 0.8.13Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: RustSec Advisory Database · CC0-1.0