Deps.rs

bevy_animation 0.15.1

[![dependency status](https://deps.rs/crate/bevy_animation/0.15.1/status.svg)](https://deps.rs/crate/bevy_animation/0.15.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 bevy_animation

Dependencies

(24 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 bevy_app^0.15.10.15.1up to date
 bevy_asset^0.15.10.15.1up to date
 bevy_color^0.15.20.15.2up to date
 bevy_core^0.15.10.15.1up to date
 bevy_derive^0.15.10.15.1up to date
 bevy_ecs^0.15.10.15.1up to date
 bevy_hierarchy^0.15.10.15.1up to date
 bevy_log^0.15.10.15.1up to date
 bevy_math^0.15.10.15.1up to date
 bevy_reflect^0.15.10.15.1up to date
 bevy_render^0.15.10.15.1up to date
 bevy_time^0.15.10.15.1up to date
 bevy_transform^0.15.10.15.1up to date
 bevy_utils^0.15.10.15.1up to date
 blake3^1.01.5.5up to date
 derive_more^11.0.0up to date
 downcast-rs^1.2.02.0.1out of date
 either^1.131.13.0up to date
 petgraph^0.60.7.1out of date
 ron^0.80.8.1up to date
 serde^11.0.217up to date
 smallvec ⚠️^11.13.2maybe insecure
 thread_local ⚠️^11.1.8maybe insecure
 uuid^1.71.12.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.

thread_local: Data race in `Iter` and `IterMut`

RUSTSEC-2022-0006

In the affected version of this crate, {Iter, IterMut}::next used a weaker memory ordering when loading values than what was required, exposing a potential data race when iterating over a ThreadLocal's values.

Crates using Iter::next, or IterMut::next are affected by this issue.