Deps.rs

physx 0.1.2

[![dependency status](https://deps.rs/crate/physx/0.1.2/status.svg)](https://deps.rs/crate/physx/0.1.2)

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 physx

Dependencies

(10 total, 7 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 enumflags2^0.50.7.9out of date
 enumflags2_derive^0.50.7.9out of date
 floating-duration^0.1.20.1.2up to date
 log^0.40.4.21up to date
 nalgebra ⚠️^0.18.00.32.5out of date
 nalgebra-glm^0.40.18.0out of date
 ncollide3d^0.20.10.33.0out of date
 parking_lot^0.9.00.12.2out of date
 physx-macros^0.1.00.1.1up to date
 physx-sys^0.1.00.11.5out 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.