mirror of
https://github.com/OMGeeky/advisory-db.git
synced 2026-01-01 09:10:25 +01:00
782efebde9
This reverts commit 0a981e2b6f.
These now need to use the new `affected_paths` attribute, which has a
different (VersionReq-bucketed) format.
23 lines
921 B
TOML
23 lines
921 B
TOML
[advisory]
|
|
id = "RUSTSEC-2018-0003"
|
|
package = "smallvec"
|
|
unaffected_versions = ["< 0.3.2"]
|
|
patched_versions = [">= 0.6.3", "^0.3.4", "^0.4.5", "^0.5.1"]
|
|
url = "https://github.com/servo/rust-smallvec/issues/96"
|
|
keywords = ["memory-corruption"]
|
|
title = "Possible double free during unwinding in SmallVec::insert_many"
|
|
date = "2018-07-19"
|
|
description = """
|
|
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.
|
|
"""
|