This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate glib

Dependencies

(12 total, 3 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 bitflags^1.01.3.2up to date
 glib-sys^0.14.00.16.3out of date
 futures-channel^0.30.3.25up to date
 futures-core^0.30.3.25up to date
 futures-executor^0.30.3.25up to date
 futures-task ⚠️^0.30.3.25maybe insecure
 glib-macros^0.14.00.16.3out of date
 gobject-sys^0.14.00.16.3out of date
 libc^0.20.2.138up to date
 once_cell^1.01.16.0up to date
 log^0.40.4.17up to date
 smallvec ⚠️^1.01.10.0maybe insecure

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 futures-util^0.30.3.25up to date
 tempfile^33.3.0up to date

Security Vulnerabilities

futures-task: futures_task::waker may cause a use-after-free if used on a type that isn't 'static

RUSTSEC-2020-0060

Affected versions of the crate did not properly implement a 'static lifetime bound on the waker function. This resulted in a use-after-free if Waker::wake() is called after original data had been dropped.

The flaw was corrected by adding 'static lifetime bound to the data waker takes.

smallvec: Buffer overflow in SmallVec::insert_many

RUSTSEC-2021-0003

A bug in the SmallVec::insert_many method caused it to allocate a buffer that was smaller than needed. It then wrote past the end of the buffer, causing a buffer overflow and memory corruption on the heap.

This bug was only triggered if the iterator passed to insert_many yielded more items than the lower bound returned from its size_hint method.

The flaw was corrected in smallvec 0.6.14 and 1.6.1, by ensuring that additional space is always reserved for each item inserted. The fix also simplified the implementation of insert_many to use less unsafe code, so it is easier to verify its correctness.

Thank you to Yechan Bae (@Qwaz) and the Rust group at Georgia Tech’s SSLab for finding and reporting this bug.