orx-split-vec
Affected
- introduced
0.0.0-0, fixed4.0.0(semver)
Fixed versions
4.0.0
Fix
- Fixed version
4.0.0cargo update -p orx-split-vec --precise 4.0.0
Advisory
Also known as: None
Panic-safety unsoundness in SplitVec::extend_from_slice (uninitialized read)
SplitVec::extend_from_slice increments the logical length self.len before cloning the incoming elements into the reserved slots. If an element's Clone panics mid-fill, unwinding leaves self.len counting slots that were never initialized. A later safe read (get, indexing, iter) then reads one of those uninitialized slots.
This is reachable from safe Rust — a read of uninitialized memory (CWE-908). It is not a double-free: SplitVec has no manual Drop and its elements live in a standard Vec, so the defect is a read, not a free.
Impact
A safe read after the panic returns a value built from uninitialized bytes. For a heap-owning element type such as String, the resulting value has garbage length/pointer fields.
Confirmed under Miri. AddressSanitizer stays silent for this class, since the uninitialized bytes are consumed as a non-dereferenced field rather than an invalid load or free.
Fix
Fixed in orx-split-vec 4.0.0, which no longer commits the length before the elements are cloned.
Not rated by the source.
0.0.0-0, fixed 4.0.0 (semver)4.0.0
4.0.0cargo update -p orx-split-vec --precise 4.0.0Fix 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