Deps.rs

amethyst_core 0.15.3

[![dependency status](https://deps.rs/crate/amethyst_core/0.15.3/status.svg)](https://deps.rs/crate/amethyst_core/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_core

Dependencies

(16 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 alga^0.9.20.9.3up to date
 alga_derive^0.9.10.9.2up to date
 amethyst_error^0.15.30.15.3up to date
 approx^0.3.20.5.1out of date
 derivative^2.1.12.2.0up to date
 derive-new^0.5.80.7.0out of date
 fnv^1.0.61.0.7up to date
 getset^0.0.90.1.3out of date
 log^0.4.80.4.22up to date
 nalgebra ⚠️^0.19.00.33.2out of date
 num-traits^0.2.110.2.19up to date
 rayon^1.3.01.10.0up to date
 serde^11.0.215up to date
 specs^0.16.00.20.0out of date
 specs-hierarchy^0.60.6.0up to date
 thread_profiler^0.30.3.0up to date

Security Vulnerabilities

nalgebra: VecStorage Deserialize Allows Violation of Length Invariant

RUSTSEC-2021-0070

The Deserialize implementation for VecStorage did not maintain the invariant that the number of elements must equal nrows * ncols. Deserialization of specially crafted inputs could allow memory access beyond allocation of the vector.

This flaw was introduced in v0.11.0 (086e6e) due to the addition of an automatically derived implementation of Deserialize for MatrixVec. MatrixVec was later renamed to VecStorage in v0.16.13 (0f66403) and continued to use the automatically derived implementation of Deserialize.

This flaw was corrected in commit 5bff536 by returning an error during deserialization if the number of elements does not exactly match the expected size.