mirror of
https://github.com/OMGeeky/advisory-db.git
synced 2026-01-20 18:41:03 +01:00
ac125ee29a
As proposed in #240 and tracked in #414, this PR translates all advisories into the new "V3" advisory format, which is based on Markdown with leading TOML front matter. This format makes it easier to see rendered Markdown syntax descriptions, whether rendered by an IDE or GitHub. This should help with both crafting advisories initially as well as review, and ideally encourages more lengthy descriptions. Support for this format shipped in `cargo-audit` v0.12.0 on May 6th, 2020.
31 lines
1.2 KiB
Markdown
31 lines
1.2 KiB
Markdown
```toml
|
|
[advisory]
|
|
id = "RUSTSEC-2018-0008"
|
|
package = "slice-deque"
|
|
aliases = ["CVE-2018-20995"]
|
|
date = "2018-12-05"
|
|
keywords = ["memory-corruption", "rce"]
|
|
url = "https://github.com/gnzlbg/slice_deque/issues/57"
|
|
|
|
[versions]
|
|
patched = [">= 0.1.16"]
|
|
```
|
|
|
|
# Bug in SliceDeque::move_head_unchecked allows read of corrupted memory
|
|
|
|
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.
|