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.
tract-tensorflow(11 total, 7 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bytes | ^0.4.7 | 1.6.0 | out of date |
| derive-new | ^0.5 | 0.6.0 | out of date |
| error-chain | ^0.12 | 0.12.4 | up to date |
| itertools | ^0.8 | 0.12.1 | out of date |
| log | ^0.4 | 0.4.21 | up to date |
| num-traits | ^0.2 | 0.2.18 | up to date |
| prost ⚠️ | ^0.5 | 0.12.4 | out of date |
| prost-types ⚠️ | ^0.5 | 0.12.4 | out of date |
| tensorflow | ^0 | 0.21.0 | up to date |
| tract-core | ^0.5.8 | 0.21.3 | out of date |
| tract-linalg | ^0.5.8 | 0.21.3 | out of date |
(4 total, 4 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| criterion | ^0.3 | 0.5.1 | out of date |
| env_logger | ^0.7 | 0.11.3 | out of date |
| proptest | ^0.9 | 1.4.0 | out of date |
| rand | ^0.7 | 0.8.5 | out of date |
prost: Parsing a specially crafted message can result in a stack overflowAffected versions of this crate contained a bug in which decoding untrusted input could overflow the stack.
On architectures with stack probes (like x86), this can be used for denial of service attacks, while on architectures without stack probes (like ARM) overflowing the stack is unsound and can result in potential memory corruption (or even RCE).
The flaw was quickly corrected by @danburkert and released in version 0.6.1.
prost-types: Conversion from `prost_types::Timestamp` to `SystemTime` can cause an overflow and panicAffected versions of this crate contained a bug in which untrusted input could cause an overflow and panic when converting a Timestamp to SystemTime.
It is recommended to upgrade to prost-types v0.8 and switch the usage of From<Timestamp> for SystemTime to TryFrom<Timestamp> for SystemTime.
See #438 for more information.