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.
mps(10 total, 3 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| cfg-if | ^1.0.0 | 1.0.4 | up to date |
| clap | ^4.5 | 4.5.52 | up to date |
| color-eyre | ^0.6 | 0.6.5 | up to date |
| fast-float2 ⚠️ | ^0.2 | 0.2.3 | maybe insecure |
| hashbrown ⚠️ | ^0.15 | 0.16.0 | out of date |
| indexmap | ^2.0 | 2.12.0 | up to date |
| nom | ^7.1 | 8.0.0 | out of date |
| nom-tracable | ^0.9 | 0.9.1 | up to date |
| nom_locate | ^4.2 | 5.0.0 | out of date |
| serde | ^1.0 | 1.0.228 | up to date |
(3 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| criterion | ^0.5 | 0.7.0 | out of date |
| insta | ^1.41 | 1.43.2 | up to date |
| proptest | ^1.6 | 1.9.0 | up to date |
hashbrown: Borsh serialization of HashMap is non-canonicalThe borsh serialization of the HashMap did not follow the borsh specification. It potentially produced non-canonical encodings dependent on insertion order. It also did not perform canonicty checks on decoding.
This can result in consensus splits and cause equivalent objects to be considered distinct.
This was patched in 0.15.1.
fast-float2: Segmentation fault due to lack of bound checkIn this case, the "fast_float2::common::AsciiStr::first" method within the "AsciiStr" struct uses the unsafe keyword to reading from memory without performing bounds checking. Specifically, it directly dereferences a pointer offset by "self.ptr". Because of the above reason, the method accesses invalid memory address when it takes an empty string as its input. This approach violates Rust’s memory safety guarantees, as it can lead to invalid memory access if empty buffer is provided.