mirror of
https://github.com/OMGeeky/advisory-db.git
synced 2026-01-18 09:24:34 +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.1 KiB
Markdown
31 lines
1.1 KiB
Markdown
```toml
|
|
[advisory]
|
|
id = "RUSTSEC-2019-0002"
|
|
package = "slice-deque"
|
|
aliases = ["CVE-2019-15543"]
|
|
date = "2019-05-07"
|
|
keywords = ["memory-corruption", "rce"]
|
|
references = ["RUSTSEC-2018-0008"]
|
|
url = "https://github.com/gnzlbg/slice_deque/issues/57"
|
|
|
|
[versions]
|
|
patched = [">= 0.2.0"]
|
|
```
|
|
|
|
# Bug in SliceDeque::move_head_unchecked corrupts its memory
|
|
|
|
Affected versions of this crate entered a corrupted state if
|
|
`mem::size_of::<T>() % allocation_granularity() != 0` and a specific allocation
|
|
pattern was used: sufficiently shifting the deque elements over the mirrored
|
|
page boundary.
|
|
|
|
This allows an attacker that controls controls both element insertion and
|
|
removal to corrupt the deque, such that reading elements from it would read
|
|
bytes corresponding to other elements in the deque. (e.g. a read of T could read
|
|
some bytes from one value and some bytes from an adjacent one, resulting in a T
|
|
whose value representation is not meaningful). This is undefined behavior.
|
|
|
|
The flaw was corrected by using a pair of pointers to track the head and tail of
|
|
the deque instead of a pair of indices. This pair of pointers are represented
|
|
using a Rust slice.
|