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

Crate crayon

Dependencies

(17 total, 7 outdated, 1 insecure)

CrateRequiredLatestStatus
 bincode^1.0.13.0.0out of 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.8insecure
 failure^0.1.20.1.8up to date
 gl^0.10.00.14.0out of date
 glutin^0.18.00.32.3out of date
 inlinable_string^0.1.100.1.15up to date
 js-sys^0.3.60.3.105up to date
 log^0.4.50.4.34up to date
 serde^1.0.791.0.229up to date
 serde_json^1.0.321.0.151up to date
 smallvec^0.6.51.16.1out of date
 uuid^0.7.11.26.1out of date
 wasm-bindgen^0.2.290.2.128up to date
 web-sys^0.3.60.3.105up to date

Dev dependencies

(2 total, 2 outdated)

CrateRequiredLatestStatus
 env_logger^0.6.00.11.11out of date
 rand^0.5.50.10.2out of date

Security Vulnerabilities

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.