rustsec/advisory-db
1
0
Fork 0
mirror of https://github.com/rustsec/advisory-db.git synced 2025-12-27 01:54:07 -05:00
Code Issues Packages Projects Releases Wiki Activity
Files
ac125ee29a3b934fc00f52bf56031dc837e9384d
advisory-db/crates/smallvec/RUSTSEC-2018-0003.md
Tony Arcieri ac125ee29a Translate database into V3 advisory format (#420) 
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.
2020-10-01 18:29:11 -07:00

928 B
Raw Blame History 

[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.