CVE-2018-20991Critical· 9.8▾ MidnightPossible double free during unwinding in SmallVec::insert_many
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 53.9 · likelihood 0.3 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 17.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
1.8%
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.
smallvec >= 0.6.0-0, < 0.6.3Upgrade to a patched release:
smallvec 0.6.3Connected by shared product, vendor, weakness, or advisory.
CVE-2021-25900Critical· 9.8Buffer overflow in SmallVec::insert_many
CVE-2019-15554Critical· 9.8Memory corruption in SmallVec::grow()
CVE-2019-15551Critical· 9.8Double-free and use-after-free in SmallVec::grow()