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 rv

Dependencies

(10 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 doc-comment^0.30.3.3up to date
 getset^0.0.70.1.2out of date
 nalgebra ⚠️^0.180.32.4out of date
 num^0.20.4.1out of date
 once_cell^11.19.0up to date
 rand^0.70.8.5out of date
 rand_distr^0.20.4.3out of date
 serde^11.0.197up to date
 serde_derive^11.0.197up to date
 special^0.80.10.3out of date

Dev dependencies

(4 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 assert^0.70.7.5up to date
 criterion^0.20.5.1out of date
 indoc^0.32.0.5out of date
 serde_yaml ⚠️^0.80.9.34+deprecatedout of date

Security Vulnerabilities

serde_yaml: Uncontrolled recursion leads to abort in deserialization

RUSTSEC-2018-0005

Affected versions of this crate did not properly check for recursion while deserializing aliases.

This allows an attacker to make a YAML file with an alias referring to itself causing an abort.

The flaw was corrected by checking the recursion depth.

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.