reorder
Affected
- introduced
0.0.0-0, fixed1.1.0(semver)
Fixed versions
1.1.0
Fix
- Fixed version
1.1.0cargo update -p reorder --precise 1.1.0
Advisory
Also known as: CVE-2021-29941, CVE-2021-29942, GHSA-3h87-v52r-p9rg, GHSA-jpwg-6gf5-5vh9
swap_index can write out of bounds and return uninitialized memory
swap_index takes an iterator and swaps the items with their corresponding
indexes. It reserves capacity and sets the length of the vector based on the.len() method of the iterator.
If the len() returned by the iterator is larger than the actual number of
elements yielded, then swap_index creates a vector containing uninitialized
members. If the len() returned by the iterator is smaller than the actual
number of members yielded, then swap_index can write out of bounds past
its allocated vector.
As noted by the Rust documentation, `len()`
and size_hint() are primarily meant for optimization and incorrect values
from their implementations should not lead to memory safety violations.
Patch
A new version crate was pushed that marks this function as unsafe.
reorder = "1.1.0"
Previous versions have also been yanked from crates.io.
High Basis: CVSS v3 score 7.3, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
0.0.0-0, fixed 1.1.0 (semver)1.1.0
1.1.0cargo update -p reorder --precise 1.1.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