Deps.rs

pgp 0.2.4

[![dependency status](https://deps.rs/crate/pgp/0.2.4/status.svg)](https://deps.rs/crate/pgp/0.2.4)

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

Crate pgp

Dependencies

(41 total, 27 outdated, 2 insecure)

CrateRequiredLatestStatus
 aes^0.30.9.3out of date
 base64^0.10.10.23.1out of date
 bitfield^0.13.10.19.5out of date
 block-modes^0.30.9.1out of date
 block-padding^0.1.20.4.2out of date
 blowfish^0.40.10.0out of date
 buf_redux^0.8.10.8.4up to date
 byteorder^1.21.5.0up to date
 cast5^0.6.00.12.0out of date
 cfb-mode^0.3.20.9.1out of date
 chrono^0.40.4.45up to date
 circular^0.30.3.0up to date
 crc24^0.10.1.6up to date
 derive_builder^0.7.00.20.2out of date
 des^0.30.9.0out of date
 digest^0.80.11.3out of date
 ed25519-dalek ⚠️^1.0.0-pre.13.0.0insecure
 enum_primitive^0.10.1.1up to date
 failure^0.10.1.8up to date
 flate2^1.01.1.10up to date
 generic-array^0.121.4.5out of date
 gperftools^0.2.00.2.0up to date
 hex^0.40.4.3up to date
 lazy_static^1.2.01.5.1up to date
 log^0.4.60.4.34up to date
 md-5^0.80.11.0out of date
 nom^4.28.0.0out of date
 num-bigint-dig^0.50.9.1out of date
 num-derive^0.2.30.5.1out of date
 num-traits^0.2.60.2.19up to date
 rand^0.60.10.3out of date
 ripemd160^0.80.10.0out of date
 rsa ⚠️^0.1.40.9.10insecure
 sha-1^0.80.10.1out of date
 sha2^0.80.11.0out of date
 sha3^0.8.10.12.0out of date
 smallvec^0.6.91.16.2out of date
 try_from^0.30.3.2up to date
 twofish^0.20.8.0out of date
 x25519-dalek^0.53.0.0out of date
 zeroize^0.10.11.9.0out of date

Dev dependencies

(9 total, 5 outdated)

CrateRequiredLatestStatus
 glob^0.30.3.4up to date
 hex-literal^0.21.1.0out of date
 pretty_assertions^0.61.4.1out of date
 pretty_env_logger^0.30.5.0out of date
 rand_chacha^0.10.10.0out of date
 rand_xorshift^0.10.5.0out of date
 regex^1.11.13.1up to date
 serde^1.01.0.229up to date
 serde_json^1.01.0.151up to date

Security Vulnerabilities

ed25519-dalek: Double Public Key Signing Function Oracle Attack on `ed25519-dalek`

RUSTSEC-2022-0093

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 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. The crypto-bigint migration (RustCrypto/RSA#394) did not close this. Tracking is RustCrypto/RSA#626 (padding still not constant-time). Implicit rejection work is in RustCrypto/RSA#680; default-path blinding is in RustCrypto/RSA#702.

Still affected as of 2026-09-12: rsa 0.9.10 (latest stable) and rsa 0.10.0-rc.18 (latest). patched = [] is intentional.

Workarounds

Avoid using the rsa crate in settings where attackers can observe timing, for example over the network. 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.