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_core

Dependencies

(23 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.10.1.83up to date
 base64^0.220.22.1up to date
 bytes^1.01.9.0up to date
 dyn-clone^1.01.0.17up to date
 futures^0.30.3.31up to date
 getrandom^0.20.2.15up to date
 hmac^0.120.12.1up to date
 http-types^2.122.12.0up to date
 once_cell^1.181.20.2up to date
 openssl ⚠️^0.100.10.68maybe insecure
 paste^1.01.0.15up to date
 pin-project^1.01.1.7up to date
 quick-xml^0.310.37.1out of date
 rand^0.80.8.5up to date
 reqwest^0.12.00.12.9up to date
 serde^1.01.0.216up to date
 serde_json^1.01.0.134up to date
 sha2^0.100.10.8up to date
 time^0.3.100.3.37up to date
 tokio ⚠️^1.01.42.0maybe insecure
 tracing^0.1.400.1.41up to date
 url^2.22.5.4up to date
 uuid^1.01.11.0up to date

Dev dependencies

(3 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 thiserror^1.02.0.9out of date
 tokio ⚠️^1.01.42.0maybe insecure
 tracing-subscriber^0.30.3.19up 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);

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.