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 aliri_oauth2

Dependencies

(11 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 aliri^0.6.00.6.3up to date
 aliri_braid^0.2.30.4.0out of date
 aliri_clock^0.1.00.1.4up to date
 aliri_traits^0.1.00.1.1up to date
 arc-swap^1.21.7.1up to date
 reqwest^0.110.12.4out of date
 serde^11.0.199up to date
 smartstring^11.0.1up to date
 thiserror^11.0.59up to date
 tokio ⚠️^11.37.0maybe insecure
 tracing^0.1.150.1.40up to date

Dev dependencies

(4 total, 2 possibly insecure)

CrateRequiredLatestStatus
 aliri^0.6.00.6.3up to date
 openssl ⚠️^0.100.10.64maybe insecure
 serde_json^11.0.116up to date
 tokio ⚠️^11.37.0maybe 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);

openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-read

RUSTSEC-2023-0044

When this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.