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 dbus-async

Dependencies

(14 total, 5 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 log~0.4.140.4.21up to date
 futures~0.3.170.3.30up to date
 dbus-message-parser~4.3.14.3.1up to date
 dbus-server-address-parser~1.0.11.0.1up to date
 hex~0.4.30.4.3up to date
 bytes~1.1.01.6.0out of date
 lru ⚠️~0.7.00.12.3out of date
 libc~0.2.1110.2.153up to date
 bitflags~1.3.22.5.0out of date
 retain_mut~0.1.50.1.9up to date
 async-trait~0.1.520.1.80up to date
 thiserror~1.0.301.0.58up to date
 async-recursion~0.3.21.1.0out of date
 tokio ⚠️~1.15.01.37.0out of date

Dev dependencies

(1 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️~1.15.01.37.0out of date

Security Vulnerabilities

lru: Use after free in lru crate

RUSTSEC-2021-0130

Lru crate has use after free vulnerability.

Lru crate has two functions for getting an iterator. Both iterators give references to key and value. Calling specific functions, like pop(), will remove and free the value, and but it's still possible to access the reference of value which is already dropped causing use after free.

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