Deps.rs

amethyst_tiles 0.15.3

[![dependency status](https://deps.rs/crate/amethyst_tiles/0.15.3/status.svg)](https://deps.rs/crate/amethyst_tiles/0.15.3)

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 amethyst_tiles

Dependencies

(18 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 amethyst_assets^0.15.30.15.3up to date
 amethyst_core^0.15.30.15.3up to date
 amethyst_error^0.15.30.15.3up to date
 amethyst_rendy^0.15.30.15.3up to date
 amethyst_window^0.15.30.15.3up to date
 bitintr^0.30.3.0up to date
 derivative^2.1.12.2.0up to date
 err-derive^0.2.30.3.1out of date
 failure^0.10.1.8up to date
 fnv^11.0.7up to date
 glsl-layout ⚠️^0.30.5.0out of date
 hibitset^0.6.20.6.4up to date
 lazy_static^1.41.5.0up to date
 log^0.4.60.4.22up to date
 rayon^1.3.01.10.0up to date
 serde^1.01.0.215up to date
 smallvec ⚠️^1.2.01.13.2maybe insecure
 thread_profiler^0.30.3.0up to 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.

glsl-layout: Double drop upon panic in 'fn map_array()'

RUSTSEC-2021-0005

Affected versions of this crate did not guard against panic within the user-provided function f (2nd parameter of fn map_array), and thus panic within f causes double drop of a single object.

The flaw was corrected in the 0.4.0 release by wrapping the object vulnerable to a double drop within ManuallyDrop<T>.