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 zbus

Dependencies

(37 total, 14 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-broadcast^0.5.00.7.0out of date
 async-executor^1.5.01.11.0up to date
 async-fs^1.6.02.1.1out of date
 async-io^1.12.02.3.2out of date
 async-lock^2.6.03.3.0out of date
 async-recursion^1.0.01.1.0up to date
 async-task^4.3.04.7.0up to date
 async-trait^0.1.580.1.80up to date
 byteorder^1.4.31.5.0up to date
 derivative^2.22.2.0up to date
 dirs^4.0.05.0.1out of date
 enumflags2^0.7.50.7.9up to date
 event-listener^2.5.35.3.0out of date
 futures-core^0.3.250.3.30up to date
 futures-sink^0.3.250.3.30up to date
 futures-util^0.3.250.3.30up to date
 hex^0.4.30.4.3up to date
 lazy_static^1.4.01.4.0up to date
 nix^0.26.00.28.0out of date
 once_cell^1.4.01.19.0up to date
 ordered-stream^0.20.2.0up to date
 quick-xml^0.27.10.31.0out of date
 rand^0.8.50.8.5up to date
 serde^1.01.0.197up to date
 serde-xml-rs^0.4.10.6.0out of date
 serde_repr^0.1.90.1.19up to date
 sha1^0.10.50.10.6up to date
 static_assertions^1.1.01.1.0up to date
 tokio ⚠️^1.21.21.37.0maybe insecure
 tokio-vsock^0.3.30.5.0out of date
 tracing^0.1.370.1.40up to date
 uds_windows^1.0.21.1.0up to date
 vsock^0.3.00.5.0out of date
 winapi^0.30.3.9up to date
 zbus_macros=3.11.14.1.2out of date
 zbus_names^2.53.0.0out of date
 zvariant^3.10.04.0.2out of date

Dev dependencies

(8 total, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.12.01.12.0up to date
 doc-comment^0.3.30.3.3up to date
 futures-util^0.3.250.3.30up to date
 ntest^0.9.00.9.2up to date
 tempfile^3.3.03.10.1up to date
 test-log^0.2.110.2.15up to date
 tokio ⚠️^11.37.0maybe insecure
 tracing-subscriber^0.3.160.3.18up 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);