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 azure_identity

Dependencies

(15 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-lock^2.53.4.0out of date
 async-timer^1.0.0-beta.70.7.4up to date
 async-trait^0.10.1.83up to date
 azure_core^0.40.20.0out of date
 base64^0.13.00.22.1out of date
 fix-hidden-lifetime-bug^0.20.2.7up to date
 futures^0.30.3.30up to date
 log^0.40.4.22up to date
 oauth2^4.0.04.4.2up to date
 openssl ⚠️^0.100.10.66maybe insecure
 serde^1.01.0.210up to date
 serde_json^1.01.0.128up to date
 time^0.3.100.3.36up to date
 url^2.22.5.2up to date
 uuid^1.01.10.0up to date

Dev dependencies

(4 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 env_logger^0.90.11.5out of date
 reqwest^0.110.12.8out of date
 serde_test^11.0.177up to date
 tokio ⚠️^1.01.40.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: `MemBio::get_buf` has undefined behavior with empty buffers

RUSTSEC-2024-0357

Previously, MemBio::get_buf called slice::from_raw_parts with a null-pointer, which violates the functions invariants, leading to undefined behavior. In debug builds this would produce an assertion failure. This is now fixed.