aligned_box
Affected
- introduced
0.0.0-0, fixed0.3.1(semver)
Fixed versions
0.3.1
Fix
- Fixed version
0.3.1cargo update -p aligned_box --precise 0.3.1
Advisory
Also known as: None
Double free in AlignedBox<[T]>::realloc_with_default when an element's Drop panics
Shrinking an AlignedBox<[T]> takes ownership of the buffer out ofself.container with ManuallyDrop::take, destroys the elements past the new
length, and only then commits the new Box back into self.container.ManuallyDrop::take moves ownership but not the bits, so until that commitself.container still points at the original buffer.
T::drop runs inside the destruction loop and is user code — T carries no
bound that would exclude a panicking Drop. If it unwinds, the commit is
skipped and self.container is left pointing at the buffer whose tail has
already been destroyed. AlignedBox's own destructor then reconstructs a Box
from that pointer, drops every element again and deallocates — a double free
(CWE-415) / use-after-free (CWE-416) reachable from safe Rust.
Growing the slice destroys nothing and is unaffected, as isrealloc_with_value, which requires T: Copy and therefore a Drop that
cannot run.
Mitigation
Update to 0.3.1.
Not rated by the source.
0.0.0-0, fixed 0.3.1 (semver)0.3.1
0.3.1cargo update -p aligned_box --precise 0.3.1Fix 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