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

Crate mail-auth

Dependencies

(18 total, 6 outdated, 1 insecure, 1 possibly insecure)

CrateRequiredLatestStatus
 ahash^0.8.00.8.12up to date
 ed25519-dalek^2.02.1.1up to date
 flate2^1.0.251.1.2up to date
 hickory-resolver^0.240.25.2out of date
 lru-cache^0.1.20.1.2up to date
 mail-builder^0.30.4.3out of date
 mail-parser^0.90.11.0out of date
 parking_lot^0.12.00.12.4up to date
 quick-xml^0.320.38.0out of date
 rand^0.8.50.9.1out of date
 ring ⚠️^0.170.17.14maybe insecure
 rsa ⚠️^0.9.60.9.8insecure
 rustls-pemfile^22.2.0up to date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 sha1^0.100.10.6up to date
 sha2^0.10.60.10.9up to date
 zip^2.1.14.2.0out of date

Dev dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 rustls-pemfile^22.2.0up to date
 tokio ⚠️^1.161.46.1maybe insecure

Security Vulnerabilities

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);

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.

ring: Some AES functions may panic when overflow checking is enabled.

RUSTSEC-2025-0009

ring::aead::quic::HeaderProtectionKey::new_mask() may panic when overflow checking is enabled. In the QUIC protocol, an attacker can induce this panic by sending a specially-crafted packet. Even unintentionally it is likely to occur in 1 out of every 2**32 packets sent and/or received.

On 64-bit targets operations using ring::aead::{AES_128_GCM, AES_256_GCM} may panic when overflow checking is enabled, when encrypting/decrypting approximately 68,719,476,700 bytes (about 64 gigabytes) of data in a single chunk. Protocols like TLS and SSH are not affected by this because those protocols break large amounts of data into small chunks. Similarly, most applications will not attempt to encrypt/decrypt 64GB of data in one chunk.

Overflow checking is not enabled in release mode by default, but RUSTFLAGS="-C overflow-checks" or overflow-checks = true in the Cargo.toml profile can override this. Overflow checking is usually enabled by default in debug mode.