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

Crate lettre

Dependencies

(37 total, 5 outdated, 1 insecure, 2 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.81.13.2up to date
 async-trait^0.10.1.89up to date
 base64^0.220.22.1up to date
 boring^44.19.0up to date
 chumsky^0.90.11.2out of date
 ed25519-dalek^22.2.0up to date
 email-encoding^0.30.4.1out of date
 email_address^0.2.10.2.9up to date
 fastrand^2.02.3.0up to date
 futures-io^0.3.70.3.31up to date
 futures-rustls^0.260.26.0up to date
 futures-util^0.3.70.3.31up to date
 hostname^0.40.4.1up to date
 httpdate^11.0.3up to date
 idna^11.1.0up to date
 mime^0.3.40.3.17up to date
 native-tls^0.2.90.2.14up to date
 nom^78.0.0out of date
 percent-encoding^2.32.3.2up to date
 quoted_printable^0.50.5.1up to date
 rsa ⚠️^0.90.9.9insecure
 rustls ⚠️^0.23.50.23.35maybe insecure
 rustls-native-certs^0.80.8.2up to date
 rustls-pemfile^22.2.0up to date
 rustls-pki-types^1.71.13.0up to date
 serde^11.0.228up to date
 serde_json^11.0.145up to date
 sha2^0.100.10.9up to date
 socket2^0.5.10.6.1out of date
 tokio-boring^44.19.0up to date
 tokio ⚠️^11.48.0maybe insecure
 tokio-native-tls^0.30.3.1up to date
 tokio-rustls^0.260.26.4up to date
 tracing^0.1.160.1.41up to date
 url^2.42.5.7up to date
 uuid^11.18.1up to date
 webpki-roots^0.261.0.4out of date

Dev dependencies

(10 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.81.13.2up to date
 criterion^0.50.7.0out of date
 glob^0.30.3.3up to date
 maud^0.260.27.0out of date
 pretty_assertions^11.4.1up to date
 serde_json^11.0.145up to date
 tokio ⚠️^11.48.0maybe insecure
 tracing^0.1.160.1.41up to date
 tracing-subscriber ⚠️^0.30.3.20maybe insecure
 walkdir^22.5.0up to date

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.

rustls: rustls network-reachable panic in `Acceptor::accept`

RUSTSEC-2024-0399

A bug introduced in rustls 0.23.13 leads to a panic if the received TLS ClientHello is fragmented. Only servers that use rustls::server::Acceptor::accept() are affected.

Servers that use tokio-rustls's LazyConfigAcceptor API are affected.

Servers that use tokio-rustls's TlsAcceptor API are not affected.

Servers that use rustls-ffi's rustls_acceptor_accept API are affected.

tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequences

RUSTSEC-2025-0055

Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:

  • Manipulate terminal title bars
  • Clear screens or modify terminal display
  • Potentially mislead users through terminal manipulation

In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.

This was patched in PR #3368 to escape ANSI control characters from user input.