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.
sample_planning(13 total, 8 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| chrono ⚠️ | ^0.4 | 0.4.38 | maybe insecure |
| clap | ^2.32 | 4.5.4 | out of date |
| kiss3d | ^0.20.1 | 0.35.0 | out of date |
| log | ^0.4.6 | 0.4.21 | up to date |
| mazth | ^0.5.0 | 0.6.0 | out of date |
| nalgebra ⚠️ | ^0.18.0 | 0.32.5 | out of date |
| ncollide3d | ^0.19.2 | 0.33.0 | out of date |
| pretty_env_logger | ^0.3 | 0.5.0 | out of date |
| rand | ^0.6.5 | 0.8.5 | out of date |
| rayon | ^1.0.3 | 1.10.0 | up to date |
| serde | ^1.0 | 1.0.198 | up to date |
| serde_json | ^1.0 | 1.0.116 | up to date |
| zpatial | ^0.3.3 | 0.4.3 | out of date |
chrono: Potential segfault in `localtime_r` invocationsUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
No workarounds are known.
nalgebra: VecStorage Deserialize Allows Violation of Length InvariantThe 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.