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-2019-0009.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

886 B
Raw Blame History 

[advisory]
id = "RUSTSEC-2019-0009"
package = "smallvec"
aliases = ["CVE-2019-15551"]
date = "2019-06-06"
keywords = ["double free", "use after free", "arbitrary code execution"]
url = "https://github.com/servo/rust-smallvec/issues/148"

[affected.functions]
"smallvec::SmallVec::grow" = ["< 0.6.10, >= 0.6.5"]

[versions]
patched = [">= 0.6.10"]
unaffected = ["< 0.6.5"]

Double-free and use-after-free in SmallVec::grow()

Attempting to call grow on a spilled SmallVec with a value equal to the current capacity causes it to free the existing data. This performs a double free immediately and may lead to use-after-free on subsequent accesses to the SmallVec contents.

An attacker that controls the value passed to grow may exploit this flaw to obtain memory contents or gain remote code execution.

Credits to @ehuss for discovering, reporting and fixing the bug.