Deps.rs

crayon 0.7.1

[![dependency status](https://deps.rs/crate/crayon/0.7.1/status.svg)](https://deps.rs/crate/crayon/0.7.1)

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 crayon

Dependencies

(17 total, 6 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 bincode^1.0.11.3.3up to date
 byteorder^1.2.61.5.0up to date
 cgmath^0.16.10.18.0out of date
 console_error_panic_hook^0.1.50.1.7up to date
 crossbeam-deque ⚠️^0.5.10.8.5out of date
 failure^0.1.20.1.8up to date
 gl^0.10.00.14.0out of date
 glutin^0.18.00.31.3out of date
 inlinable_string^0.1.100.1.15up to date
 js-sys^0.3.60.3.69up to date
 log^0.4.50.4.21up to date
 serde^1.0.791.0.198up to date
 serde_json^1.0.321.0.116up to date
 smallvec ⚠️^0.6.51.13.2out of date
 uuid^0.7.11.8.0out of date
 wasm-bindgen^0.2.290.2.92up to date
 web-sys^0.3.60.3.69up to date

Dev dependencies

(2 total, 2 outdated)

CrateRequiredLatestStatus
 env_logger^0.6.00.11.3out of date
 rand^0.5.50.8.5out of date

Security Vulnerabilities

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.

crossbeam-deque: Data race in crossbeam-deque

RUSTSEC-2021-0093

In the affected version of this crate, the result of the race condition is that one or more tasks in the worker queue can be popped twice instead of other tasks that are forgotten and never popped. If tasks are allocated on the heap, this can cause double free and a memory leak. If not, this still can cause a logical bug.

Crates using Stealer::steal, Stealer::steal_batch, or Stealer::steal_batch_and_pop are affected by this issue.

Credits to @kmaork for discovering, reporting and fixing the bug.