Deps.rs

kiss3d 0.20.1

[![dependency status](https://deps.rs/crate/kiss3d/0.20.1/status.svg)](https://deps.rs/crate/kiss3d/0.20.1)

This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate kiss3d

Dependencies

(15 total, 8 outdated, 1 insecure)

CrateRequiredLatestStatus
 bitflags^1.02.13.2out of date
 gl^0.110.14.0out of date
 glutin^0.190.32.3out of date
 image^0.210.25.10out of date
 instant^0.10.1.13up to date
 kiss3d_conrod^0.630.64.0out of date
 libc^0.20.2.191up to date
 nalgebra ⚠️^0.180.35.0insecure
 ncollide3d^0.190.33.0out of date
 num-traits^0.20.2.19up to date
 rusttype^0.70.9.3out of date
 serde^1.01.0.229up to date
 serde_derive^1.01.0.229up to date
 stdweb^0.40.4.20up to date
 stdweb-derive^0.50.5.3up to date

Dev dependencies

(2 total, 2 outdated)

CrateRequiredLatestStatus
 ncollide2d^0.190.33.0out of date
 rand^0.60.10.3out 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.