mirror of
https://github.com/OMGeeky/advisory-db.git
synced 2025-12-30 16:24:05 +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.
28 lines
928 B
Markdown
28 lines
928 B
Markdown
```toml
|
|
[advisory]
|
|
id = "RUSTSEC-2018-0003"
|
|
package = "smallvec"
|
|
aliases = ["CVE-2018-20991"]
|
|
date = "2018-07-19"
|
|
keywords = ["memory-corruption"]
|
|
url = "https://github.com/servo/rust-smallvec/issues/96"
|
|
|
|
[versions]
|
|
patched = [">= 0.6.3", "^0.3.4", "^0.4.5", "^0.5.1"]
|
|
unaffected = ["< 0.3.2"]
|
|
```
|
|
|
|
# Possible double free during unwinding in SmallVec::insert_many
|
|
|
|
If an iterator passed to `SmallVec::insert_many` panicked in `Iterator::next`,
|
|
destructors were run during unwinding while the vector was in an inconsistent
|
|
state, possibly causing a double free (a destructor running on two copies of
|
|
the same value).
|
|
|
|
This is fixed in smallvec 0.6.3 by ensuring that the vector's length is not
|
|
updated to include moved items until they have been removed from their
|
|
original positions. Items may now be leaked if `Iterator::next` panics, but
|
|
they will not be dropped more than once.
|
|
|
|
Thank you to @Vurich for reporting this bug.
|