Deps.rs

gear 0.5.0

[![dependency status](https://deps.rs/crate/gear/0.5.0/status.svg)](https://deps.rs/crate/gear/0.5.0)

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 gear

Dependencies

(11 total, 9 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 assimp^0.3.00.3.1up to date
 failure^0.10.1.8up to date
 k^0.150.31.0out of date
 log^0.3.80.4.21out of date
 nalgebra ⚠️^0.18.00.32.5out of date
 ncollide3d^0.19.00.33.0out of date
 num-traits^0.10.2.18out of date
 rand^0.3.00.8.5out of date
 rrt^0.4.00.7.0out of date
 trajectory^0.0.10.1.0out of date
 urdf-rs^0.4.00.8.0out of date

Dev dependencies

(4 total, 4 outdated)

CrateRequiredLatestStatus
 env_logger^0.4.20.11.3out of date
 kiss3d^0.200.35.0out of date
 structopt^0.2.00.3.26out of date
 urdf-viz^0.160.45.1out of 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.