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 yup-oauth2

Dependencies

(20 total, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.381.0.95up to date
 async-trait^0.10.1.83up to date
 base64^0.220.22.1up to date
 futures^0.30.3.31up to date
 http^11.2.0up to date
 http-body-util^0.10.1.2up to date
 hyper^11.5.2up to date
 hyper-rustls^0.270.27.5up to date
 hyper-tls^0.6.00.6.0up to date
 hyper-util^0.1.50.1.10up to date
 log^0.40.4.22up to date
 percent-encoding^22.3.1up to date
 rustls ⚠️^0.230.23.20maybe insecure
 rustls-pemfile^2.0.02.2.0up to date
 seahash^44.1.0up to date
 serde^1.01.0.216up to date
 serde_json^1.01.0.134up to date
 time^0.3.70.3.37up to date
 tokio ⚠️^1.01.42.0maybe insecure
 url^22.5.4up to date

Dev dependencies

(5 total, 2 outdated)

CrateRequiredLatestStatus
 env_logger^0.100.11.6out of date
 httptest^0.160.16.1up to date
 hyper-rustls^0.270.27.5up to date
 tempfile^3.13.14.0up to date
 webbrowser^0.81.0.3out of 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 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.