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_pbr

Dependencies

(17 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 bevy_app^0.13.20.13.2up to date
 bevy_asset^0.13.20.13.2up to date
 bevy_core_pipeline^0.13.20.13.2up to date
 bevy_derive^0.13.20.13.2up to date
 bevy_ecs^0.13.20.13.2up to date
 bevy_math^0.13.20.13.2up to date
 bevy_reflect^0.13.20.13.2up to date
 bevy_render^0.13.20.13.2up to date
 bevy_transform^0.13.20.13.2up to date
 bevy_utils^0.13.20.13.2up to date
 bevy_window^0.13.20.13.2up to date
 bitflags^2.32.5.0up to date
 bytemuck^11.16.0up to date
 fixedbitset^0.40.5.7out of date
 radsort^0.10.1.0up to date
 smallvec ⚠️^1.61.13.2maybe insecure
 thread_local ⚠️^1.01.1.8maybe insecure

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.