This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate pgp

Dependencies

(58 total, 2 outdated, 1 insecure, 1 possibly insecure)

CrateRequiredLatestStatus
 aes^0.80.8.4up to date
 argon2^0.50.5.3up to date
 base64^0.22.00.22.1up to date
 bitfield^0.140.15.0out of date
 block-padding^0.3.20.3.3up to date
 blowfish^0.90.9.1up to date
 byteorder^1.41.5.0up to date
 camellia^0.10.1.0up to date
 chrono^0.4.230.4.38up to date
 cast5^0.11.00.11.1up to date
 cfb-mode^0.8.10.8.2up to date
 cipher^0.40.4.4up to date
 const-oid^0.90.9.6up to date
 crc24^0.10.1.6up to date
 derive_builder^0.20.00.20.0up to date
 des^0.80.8.1up to date
 digest^0.100.10.7up to date
 dsa^0.6.30.6.3up to date
 ecdsa^0.160.16.9up to date
 elliptic-curve^0.130.13.8up to date
 generic-array^0.141.0.0out of date
 hex^0.40.4.3up to date
 idea^0.50.5.1up to date
 iter-read^11.0.1up to date
 log^0.4.60.4.21up to date
 md-5^0.10.50.10.6up to date
 nom^7.07.1.3up to date
 num_enum^0.70.7.2up to date
 num-traits^0.2.60.2.19up to date
 p256^0.130.13.2up to date
 p384^0.130.13.0up to date
 p521^0.130.13.3up to date
 k256^0.130.13.3up to date
 rand^0.80.8.5up to date
 ripemd^0.1.30.1.3up to date
 rsa ⚠️^0.9.00.9.6insecure
 sha1^0.10.50.10.6up to date
 sha1-checked^0.100.10.0up to date
 sha2^0.10.60.10.8up to date
 sha3^0.10.50.10.8up to date
 signature^2.0.02.2.0up to date
 smallvec^1.8.01.13.2up to date
 thiserror^1.0.301.0.61up to date
 twofish^0.70.7.1up to date
 zeroize^1.51.8.1up to date
 getrandom^0.20.2.15up to date
 bstr^1.4.01.9.1up to date
 hkdf^0.12.40.12.4up to date
 aes-gcm^0.10.30.10.3up to date
 eax^0.5.00.5.0up to date
 ocb3^0.10.1.0up to date
 buffer-redux^1.0.01.0.1up to date
 curve25519-dalek ⚠️^4.1.24.1.3maybe insecure
 ed25519-dalek^2.0.02.1.1up to date
 flate2^1.01.0.30up to date
 gperftools^0.2.00.2.0up to date
 num-bigint-dig^0.8.10.8.4up to date
 x25519-dalek^2.0.12.0.1up to date

Dev dependencies

(10 total, all up-to-date)

CrateRequiredLatestStatus
 glob^0.30.3.1up to date
 hex-literal^0.40.4.1up to date
 pretty_assertions^11.4.0up to date
 pretty_env_logger^0.50.5.0up to date
 rand_chacha^0.30.3.1up to date
 rand_xorshift^0.30.3.0up to date
 regex^1.71.10.5up to date
 serde^1.01.0.203up to date
 serde_json^1.01.0.118up to date
 criterion^0.50.5.1up to date

Security Vulnerabilities

rsa: Marvin Attack: potential key recovery through timing sidechannels

RUSTSEC-2023-0071

Impact

Due 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.

Patches

No patch is yet available, however work is underway to migrate to a fully constant-time implementation.

Workarounds

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.

References

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.

curve25519-dalek: Timing variability in `curve25519-dalek`'s `Scalar29::sub`/`Scalar52::sub`

RUSTSEC-2024-0344

Timing variability of any kind is problematic when working with potentially secret values such as elliptic curve scalars, and such issues can potentially leak private keys and other secrets. Such a problem was recently discovered in curve25519-dalek.

The Scalar29::sub (32-bit) and Scalar52::sub (64-bit) functions contained usage of a mask value inside a loop where LLVM saw an opportunity to insert a branch instruction (jns on x86) to conditionally bypass this code section when the mask value is set to zero as can be seen in godbolt:

A similar problem was recently discovered in the Kyber reference implementation:

https://groups.google.com/a/list.nist.gov/g/pqc-forum/c/hqbtIGFKIpU/m/cnE3pbueBgAJ

As discussed on that thread, one portable solution, which is also used in this PR, is to introduce a volatile read as an optimization barrier, which prevents the compiler from optimizing it away.

The fix can be validated in godbolt here:

The problem was discovered and the solution independently verified by Alexander Wagner [email protected] and Lea Themint [email protected] using their DATA tool:

https://github.com/Fraunhofer-AISEC/DATA