This project contains known security vulnerabilities. Find detailed information at the bottom.
sequoia-openpgp(55 total, 11 outdated, 1 insecure, 5 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| aes | ^0.8 | 0.8.4 | up to date |
| aes-gcm ⚠️ | ^0.10 | 0.10.3 | maybe insecure |
| anyhow | ^1.0.18 | 1.0.102 | up to date |
| base64 | >=0.21, <0.23 | 0.22.1 | up to date |
| block-padding | ^0.3 | 0.4.2 | out of date |
| blowfish | ^0.9 | 0.9.1 | up to date |
| botan | >=0.10.6, <0.12 | 0.12.0 | out of date |
| buffered-reader | ^1.3.0 | 1.4.0 | up to date |
| bzip2 ⚠️ | >=0.4, <0.6 | 0.6.1 | out of date |
| camellia | ^0.1 | 0.1.0 | up to date |
| cast5 | ^0.11 | 0.11.1 | up to date |
| cfb-mode | ^0.8 | 0.8.2 | up to date |
| chrono ⚠️ | ^0.4.10 | 0.4.44 | maybe insecure |
| cipher | ^0.4 | 0.5.1 | out of date |
| des | ^0.8 | 0.8.1 | up to date |
| digest | ^0.10 | 0.11.2 | out of date |
| dsa | ^0.6 | 0.6.3 | up to date |
| dyn-clone | ^1 | 1.0.20 | up to date |
| eax | ^0.5 | 0.5.0 | up to date |
| ecb | ^0.1 | 0.1.2 | up to date |
| ecdsa | ^0.16 | 0.16.9 | up to date |
| ed25519 | ^2 | 2.2.3 | up to date |
| ed25519-dalek | ^2 | 2.2.0 | up to date |
| flate2 | ^1.0.1 | 1.1.9 | up to date |
| getrandom | ^0.2 | 0.4.2 | out of date |
| idea | ^0.5 | 0.5.1 | up to date |
| idna | >=1.0.3, <2 | 1.1.0 | up to date |
| lalrpop-util | ^0.20 | 0.23.1 | out of date |
| lazy_static | ^1.4.0 | 1.5.0 | up to date |
| libc | ^0.2.66 | 0.2.183 | up to date |
| md-5 | ^0.10 | 0.10.6 | up to date |
| memsec | >=0.5, <0.8 | 0.7.0 | up to date |
| nettle | ^7.3 | 7.4.0 | up to date |
| num-bigint-dig | ^0.8 | 0.9.1 | out of date |
| once_cell | ^1 | 1.21.4 | up to date |
| openssl ⚠️ | ^0.10.55 | 0.10.76 | maybe insecure |
| openssl-sys | ^0.9.90 | 0.9.112 | up to date |
| p256 | ^0.13 | 0.13.2 | up to date |
| p384 | ^0.13 | 0.13.1 | up to date |
| p521 | ^0.13 | 0.13.3 | up to date |
| rand | ^0.8 | 0.10.0 | out of date |
| rand_core | ^0.6 | 0.10.0 | out of date |
| regex ⚠️ | ^1 | 1.12.3 | maybe insecure |
| regex-syntax | ^0.8 | 0.8.10 | up to date |
| ripemd | ^0.1 | 0.1.3 | up to date |
| rsa ⚠️ | ^0.9.0 | 0.9.10 | insecure |
| sha1collisiondetection | ^0.3.1 | 0.3.4 | up to date |
| sha2 | ^0.10 | 0.10.9 | up to date |
| thiserror | ^1.0.2 | 2.0.18 | out of date |
| twofish | ^0.7 | 0.7.1 | up to date |
| typenum | ^1.12.0 | 1.19.0 | up to date |
| win-crypto-ng | ^0.5.1 | 0.5.1 | up to date |
| winapi | ^0.3.8 | 0.3.9 | up to date |
| x25519-dalek | ^2 | 2.0.1 | up to date |
| xxhash-rust | ^0.8 | 0.8.15 | up to date |
(4 total, 2 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| criterion | ^0.5 | 0.8.2 | out of date |
| quickcheck | ^1 | 1.1.0 | up to date |
| rand | ^0.8 | 0.10.0 | out of date |
| rpassword | ^7.0 | 7.4.0 | up to date |
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.
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.
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.
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.
aes-gcm: Plaintext exposed in decrypt_in_place_detached even on tag verification failureIn the AES GCM implementation of decrypt_in_place_detached, the decrypted ciphertext (i.e. the correct plaintext) is exposed even if tag verification fails.
If a program using the aes-gcm crate's decrypt_in_place* APIs accesses the buffer after decryption failure, it will contain a decryption of an unauthenticated input. Depending on the specific nature of the program this may enable Chosen Ciphertext Attacks (CCAs) which can cause a catastrophic breakage of the cipher including full plaintext recovery.
As seen in the implementation of decrypt_in_place_detached for AES GCM, if the tag verification fails, an error is returned. Because the decryption of the ciphertext is done in place, the plaintext contents are now exposed via buffer.
This should ideally not be the case - as noted in page 17 of NIST's publication Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC:
In Step 8, the result of Step 7 is compared with the authentication tag that was received as an input: if they are identical, then the plaintext is returned; otherwise,FAIL is returned.
This is seems correctly addressed in the AES GCM SIV implementation, where the decrypted buffer is encrypted again before the error is returned - this fix is straightforward to implement in AES GCM. To ensure that these types of cases are covered during testing, it would be valuable to add test cases like 23, 24 etc from project wycheproof to ensure that when a bad tag is used, there is an error on decryption and that the plaintext value is not exposed.
To reproduce this issue, I'm using test case 23 from project wycheproof.
let key = GenericArray::from_slice(&hex!("000102030405060708090a0b0c0d0e0f"));
let nonce = GenericArray::from_slice(&hex!("505152535455565758595a5b"));
let tag = GenericArray::from_slice(&hex!("d9847dbc326a06e988c77ad3863e6083")); // bad tag
let mut ct = hex!("eb156d081ed6b6b55f4612f021d87b39");
let msg = hex!("202122232425262728292a2b2c2d2e2f");
let aad = hex!("");
let cipher = Aes128Gcm::new(&key);
let _plaintext = cipher.decrypt_in_place_detached(&nonce, &aad, &mut ct, &tag);
assert_eq!(ct, msg);
openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.
In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).
The maintainers thank quitbug for reporting this vulnerability to us.