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.
zip(12 total, 4 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| aes | ^0.8.2 | 0.8.4 | up to date |
| byteorder | ^1.4.3 | 1.5.0 | up to date |
| bzip2 ⚠️ | ^0.4.3 | 0.6.1 | out of date |
| constant_time_eq | ^0.1.5 | 0.4.2 | out of date |
| crc32fast | ^1.3.2 | 1.5.0 | up to date |
| crossbeam-utils | ^0.8.8 | 0.8.21 | up to date |
| flate2 | ^1.0.23 | 1.1.9 | up to date |
| hmac | ^0.12.1 | 0.12.1 | up to date |
| pbkdf2 | ^0.11.0 | 0.12.2 | out of date |
| sha1 | ^0.10.1 | 0.10.6 | up to date |
| time ⚠️ | ^0.3.7 | 0.3.47 | maybe insecure |
| zstd | ^0.11.2 | 0.13.3 | out of date |
(4 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bencher | ^0.1.5 | 0.1.5 | up to date |
| getrandom | ^0.2.5 | 0.4.2 | out of date |
| time ⚠️ | ^0.3.7 | 0.3.47 | maybe insecure |
| walkdir | ^2.3.2 | 2.5.0 | up to date |
bzip2: bzip2 Denial of Service (DoS)Working with specific payloads can cause a Denial of Service (DoS) vector.
Both Decompress and Compress implementations can enter into infinite loops
given specific payloads entered that trigger it.
The issue is described in great detail in the bzip2 repository issue.
Thanks to bjrjk for finding and providing the patch for the issue and the maintainer responsibly responding to release a fix quickly.
Users who use the crate with untrusted data should update the bzip2 to 0.4.4.
time: Denial of Service via Stack ExhaustionWhen user-provided input is provided to any type that parses with the RFC 2822 format, a denial of service attack via stack exhaustion is possible. The attack relies on formally deprecated and rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary, non-malicious input will never encounter this scenario.
A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned rather than exhausting the stack.
Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of the stack consumed would be at most a factor of the length of the input.