slice-deque
Affected
- introduced
0, fixed0.1.16(semver)
Fixed versions
0.1.16
Fix
- Fixed version
0.1.16cargo update -p slice-deque --precise 0.1.16
Advisory
Also known as: CVE-2018-20995, RUSTSEC-2018-0008
Memory corruption slice-deque
Affected versions of this crate did not properly update the head and tail of the deque when inserting and removing elements from the front if, before insertion or removal, the tail of the deque was in the mirrored memory region, and if, after insertion or removal, the head of the deque is exactly at the beginning of the mirrored memory region.
An attacker that controls both element insertion and removal into the deque could put it in a corrupted state. Once the deque enters such an state, its head and tail are corrupted, but in bounds of the allocated memory. This can result in partial reads and writes, reads of uninitialized memory, reads of memory containing previously dropped objects, etc. An attacker could exploit this to alter program execution.
The flaw was corrected by properly updating the head and tail of the deque in this case.
Critical Basis: The source's own band: CRITICAL
0, fixed 0.1.16 (semver)0.1.16
0.1.16cargo update -p slice-deque --precise 0.1.16Fix 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: GitHub Advisory Database (reviewed advisories) · CC BY 4.0