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

Crate tracing-subscriber

Dependencies

(15 total, 1 outdated, 1 insecure, 1 possibly insecure)

CrateRequiredLatestStatus
 ansi_term^0.120.12.1up to date
 chrono ⚠️^0.4.160.4.19insecure
 lazy_static^11.4.0up to date
 matchers^0.0.10.1.0out of date
 parking_lot>=0.7, <=0.110.11.2up to date
 regex^11.5.4up to date
 serde^1.01.0.130up to date
 serde_json^1.01.0.72up to date
 sharded-slab^0.1.00.1.4up to date
 smallvec ⚠️^11.7.0maybe insecure
 thread_local^1.0.11.1.3up to date
 tracing^0.10.1.29up to date
 tracing-core^0.1.200.1.21up to date
 tracing-log^0.1.20.1.2up to date
 tracing-serde^0.1.20.1.2up to date

Dev dependencies

(7 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 criterion^0.30.3.5up to date
 log^0.40.4.14up to date
 regex^11.5.4up to date
 tokio ⚠️^0.21.14.0out of date
 tracing^0.10.1.29up to date
 tracing-futures^0.20.2.5up to date
 tracing-log^0.1.20.1.2up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

Workarounds

No workarounds are known.

References

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.

tokio: Data race when sending and receiving after closing a `oneshot` channel

RUSTSEC-2021-0124

If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv.

When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.

Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.

See tokio#4225 for more details.