This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate glib

Dependencies

(11 total, 2 outdated, 2 insecure)

CrateRequiredLatestStatus
 bitflags^1.01.2.1up to date
 futures-channel^0.30.3.13up to date
 futures-core^0.30.3.13up to date
 futures-executor^0.30.3.13up to date
 futures-preview^0.3.0-alpha0.2.2up to date
 futures-task^0.30.3.13insecure
 futures-util^0.30.3.13insecure
 glib-sys^0.9.10.10.1out of date
 gobject-sys^0.9.10.10.0out of date
 lazy_static^1.21.4.0up to date
 libc^0.20.2.86up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 tempfile^33.2.0up to date

Security Vulnerabilities

futures-util: MutexGuard::map can cause a data race in safe code

RUSTSEC-2020-0059

Affected versions of the crate had a Send/Sync implementation for MappedMutexGuard that only considered variance on T, while MappedMutexGuard dereferenced to U.

This could of led to data races in safe Rust code when a closure used in MutexGuard::map() returns U that is unrelated to T.

The issue was fixed by fixing Send and Sync implementations, and by adding a PhantomData<&'a mut U> marker to the MappedMutexGuard type to tell the compiler that the guard is over U too.

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.