This project contains known security vulnerabilities. Find detailed information at the bottom.
pgp(41 total, 27 outdated, 1 insecure, 4 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| aes | ^0.3 | 0.8.4 | out of date |
| base64 | ^0.10.1 | 0.22.0 | out of date |
| bitfield | ^0.13.1 | 0.15.0 | out of date |
| block-modes | ^0.3 | 0.9.1 | out of date |
| block-padding | ^0.1.2 | 0.3.3 | out of date |
| blowfish | ^0.4 | 0.9.1 | out of date |
| buf_redux | ^0.8.1 | 0.8.4 | up to date |
| byteorder | ^1.2 | 1.5.0 | up to date |
| cast5 | ^0.6.0 | 0.11.1 | out of date |
| cfb-mode | ^0.3.2 | 0.8.2 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.38 | maybe insecure |
| circular | ^0.3 | 0.3.0 | up to date |
| crc24 | ^0.1 | 0.1.6 | up to date |
| derive_builder | ^0.7.0 | 0.20.0 | out of date |
| des | ^0.3 | 0.8.1 | out of date |
| digest | ^0.8 | 0.10.7 | out of date |
| ed25519-dalek ⚠️ | ^1.0.0-pre.1 | 2.1.1 | out of date |
| enum_primitive | ^0.1 | 0.1.1 | up to date |
| failure | ^0.1 | 0.1.8 | up to date |
| flate2 | ^1.0 | 1.0.28 | up to date |
| generic-array ⚠️ | ^0.12 | 1.0.0 | out of date |
| gperftools | ^0.2.0 | 0.2.0 | up to date |
| hex | ^0.4 | 0.4.3 | up to date |
| lazy_static | ^1.2.0 | 1.4.0 | up to date |
| log | ^0.4.6 | 0.4.21 | up to date |
| md-5 | ^0.8 | 0.10.6 | out of date |
| nom | ^4.2 | 7.1.3 | out of date |
| num-bigint-dig | ^0.5 | 0.8.4 | out of date |
| num-derive | ^0.2.3 | 0.4.2 | out of date |
| num-traits | ^0.2.6 | 0.2.18 | up to date |
| rand | ^0.6 | 0.8.5 | out of date |
| ripemd160 | ^0.8 | 0.10.0 | out of date |
| rsa ⚠️ | ^0.1.4 | 0.9.6 | insecure |
| sha-1 | ^0.8 | 0.10.1 | out of date |
| sha2 | ^0.8 | 0.10.8 | out of date |
| sha3 | ^0.8.1 | 0.10.8 | out of date |
| smallvec ⚠️ | ^0.6.9 | 1.13.2 | out of date |
| try_from | ^0.3 | 0.3.2 | up to date |
| twofish | ^0.2 | 0.7.1 | out of date |
| x25519-dalek | ^0.5 | 2.0.1 | out of date |
| zeroize | ^0.10.1 | 1.7.0 | out of date |
(9 total, 5 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| glob | ^0.3 | 0.3.1 | up to date |
| hex-literal | ^0.2 | 0.4.1 | out of date |
| pretty_assertions | ^0.6 | 1.4.0 | out of date |
| pretty_env_logger | ^0.3 | 0.5.0 | out of date |
| rand_chacha | ^0.1 | 0.3.1 | out of date |
| rand_xorshift | ^0.1 | 0.3.0 | out of date |
| regex ⚠️ | ^1.1 | 1.10.4 | maybe insecure |
| serde | ^1.0 | 1.0.198 | up to date |
| serde_json | ^1.0 | 1.0.116 | up to date |
generic-array: arr! macro erases lifetimesAffected versions of this crate allowed unsoundly extending
lifetimes using arr! macro. This may result in a variety of
memory corruption scenarios, most likely use-after-free.
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.
smallvec: Buffer overflow in SmallVec::insert_manyA bug in the SmallVec::insert_many method caused it to allocate a buffer that was smaller than needed. It then wrote past the end of the buffer, causing a buffer overflow and memory corruption on the heap.
This bug was only triggered if the iterator passed to insert_many yielded more items than the lower bound returned from its size_hint method.
The flaw was corrected in smallvec 0.6.14 and 1.6.1, by ensuring that additional space is always reserved for each item inserted. The fix also simplified the implementation of insert_many to use less unsafe code, so it is easier to verify its correctness.
Thank you to Yechan Bae (@Qwaz) and the Rust group at Georgia Tech’s SSLab for finding and reporting this bug.
regex: Regexes with large repetitions on empty sub-expressions take a very long time to parseThe Rust Security Response WG was notified that the regex crate did not
properly limit the complexity of the regular expressions (regex) it parses. An
attacker could use this security issue to perform a denial of service, by
sending a specially crafted regex to a service accepting untrusted regexes. No
known vulnerability is present when parsing untrusted input with trusted
regexes.
This issue has been assigned CVE-2022-24713. The severity of this vulnerability
is "high" when the regex crate is used to parse untrusted regexes. Other uses
of the regex crate are not affected by this vulnerability.
The regex crate features built-in mitigations to prevent denial of service
attacks caused by untrusted regexes, or untrusted input matched by trusted
regexes. Those (tunable) mitigations already provide sane defaults to prevent
attacks. This guarantee is documented and it's considered part of the crate's
API.
Unfortunately a bug was discovered in the mitigations designed to prevent untrusted regexes to take an arbitrary amount of time during parsing, and it's possible to craft regexes that bypass such mitigations. This makes it possible to perform denial of service attacks by sending specially crafted regexes to services accepting user-controlled, untrusted regexes.
All versions of the regex crate before or equal to 1.5.4 are affected by this
issue. The fix is include starting from regex 1.5.5.
We recommend everyone accepting user-controlled regexes to upgrade immediately
to the latest version of the regex crate.
Unfortunately there is no fixed set of problematic regexes, as there are practically infinite regexes that could be crafted to exploit this vulnerability. Because of this, we do not recommend denying known problematic regexes.
We want to thank Addison Crump for responsibly disclosing this to us according to the Rust security policy, and for helping review the fix.
We also want to thank Andrew Gallant for developing the fix, and Pietro Albini for coordinating the disclosure and writing this advisory.
ed25519-dalek: Double Public Key Signing Function Oracle Attack on `ed25519-dalek`Versions of ed25519-dalek prior to v2.0 model private and public keys as
separate types which can be assembled into a Keypair, and also provide APIs
for serializing and deserializing 64-byte private/public keypairs.
Such APIs and serializations are inherently unsafe as the public key is one of
the inputs used in the deterministic computation of the S part of the signature,
but not in the R value. An adversary could somehow use the signing function as
an oracle that allows arbitrary public keys as input can obtain two signatures
for the same message sharing the same R and only differ on the S part.
Unfortunately, when this happens, one can easily extract the private key.
Revised public APIs in v2.0 of ed25519-dalek do NOT allow a decoupled
private/public keypair as signing input, except as part of specially labeled
"hazmat" APIs which are clearly labeled as being dangerous if misused.
rsa: Marvin Attack: potential key recovery through timing sidechannelsDue to a non-constant-time implementation, information about the private key is leaked through timing information which is observable over the network. An attacker may be able to use that information to recover the key.
No patch is yet available, however work is underway to migrate to a fully constant-time implementation.
The only currently available workaround is to avoid using the rsa crate in settings where attackers are able to observe timing information, e.g. local use on a non-compromised computer is fine.
This vulnerability was discovered as part of the "Marvin Attack", which revealed several implementations of RSA including OpenSSL had not properly mitigated timing sidechannel attacks.