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 oauth2

Dependencies

(14 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 base64^0.130.22.1out of date
 chrono ⚠️^0.40.4.38maybe insecure
 curl^0.4.00.4.46up to date
 getrandom^0.20.2.15up to date
 http^0.21.1.0out of date
 rand^0.80.8.5up to date
 reqwest^0.110.12.4out of date
 serde^1.01.0.200up to date
 serde_json^1.01.0.116up to date
 serde_path_to_error^0.1.20.1.16up to date
 sha2^0.100.10.8up to date
 thiserror^1.01.0.59up to date
 ureq^22.9.7up to date
 url^2.12.5.0up to date

Dev dependencies

(6 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.83up to date
 async-std^1.6.31.12.0up to date
 hex^0.40.4.3up to date
 hmac^0.120.12.1up to date
 tokio ⚠️^1.01.37.0maybe insecure
 uuid^0.81.8.0out of date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

Workarounds

No workarounds are known.

References

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);