stackvector
Affected
- introduced
0.0.0-0, fixed2.0.0(semver)
Fixed versions
2.0.0
Fix
- Fixed version
2.0.0cargo update -p stackvector --precise 2.0.0
Advisory
Also known as: None
Multiple soundness issues in stackvector
Affected versions of stackvector contained multiple soundness issues that could allow safe Rust code to trigger undefined behavior.
One issue was that StackVec::length was exposed as a public field. Safe Rust code could set length to a value larger than the backing array capacity. Other safe methods, including remove, pop, and truncate, relied on length before performing unsafe pointer operations (ptr::read, ptr::copy, offset/add). If length was corrupted by safe code, these methods could perform out-of-bounds pointer arithmetic, reads, writes, or copies.
The upstream maintainer also identified additional soundness issues, including the use of mem::uninitialized in StackVec::from_vec_unchecked, which was reachable through from_vec, and Miri violations related to MaybeUninit usage.
Version 2.0.0 was released to fix the known soundness issues.
Not rated by the source.
0.0.0-0, fixed 2.0.0 (semver)2.0.0
2.0.0cargo update -p stackvector --precise 2.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