This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate sentry

Dependencies

(23 total, 3 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 curl^0.4.250.4.46up to date
 http-client^6.5.36.5.3up to date
 httpdate^1.0.01.0.3up to date
 isahc^0.9.141.7.2out of date
 log^0.4.80.4.21up to date
 native-tls^0.2.80.2.11up to date
 reqwest^0.120.12.4up to date
 rustls ⚠️^0.21.20.23.5out of date
 sentry-anyhow^0.32.30.32.3up to date
 sentry-backtrace^0.32.30.32.3up to date
 sentry-contexts^0.32.30.32.3up to date
 sentry-core^0.32.30.32.3up to date
 sentry-debug-images^0.32.30.32.3up to date
 sentry-log^0.32.30.32.3up to date
 sentry-panic^0.32.30.32.3up to date
 sentry-slog^0.32.30.32.3up to date
 sentry-tower^0.32.30.32.3up to date
 sentry-tracing^0.32.30.32.3up to date
 serde_json^1.0.481.0.116up to date
 surf^2.0.02.3.2up to date
 tokio ⚠️^1.01.37.0maybe insecure
 ureq^2.7.02.9.7up to date
 webpki-roots^0.25.10.26.1out of date

Dev dependencies

(9 total, 1 possibly insecure)

CrateRequiredLatestStatus
 actix-web^44.5.1up to date
 anyhow^1.0.301.0.82up to date
 log^0.4.80.4.21up to date
 pretty_env_logger^0.5.00.5.0up to date
 slog^2.5.22.7.0up to date
 tokio ⚠️^1.01.37.0maybe insecure
 tower^0.40.4.13up to date
 tracing^0.10.1.40up to date
 tracing-subscriber^0.30.3.18up 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);

rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input

RUSTSEC-2024-0336

If a close_notify alert is received during a handshake, complete_io does not terminate.

Callers which do not call complete_io are not affected.

rustls-tokio and rustls-ffi do not call complete_io and are not affected.

rustls::Stream and rustls::StreamOwned types use complete_io and are affected.