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 ashpd

Dependencies

(21 total, 10 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.121.13.2up to date
 enumflags2^0.70.7.12up to date
 futures-channel^0.30.3.32up to date
 futures-util^0.30.3.32up to date
 gdk4-wayland^0.70.11.0out of date
 gdk4-x11^0.70.11.0out of date
 gtk4^0.70.11.0out of date
 libc^0.20.2.183up to date
 once_cell^1.141.21.3up to date
 pipewire^0.60.9.2out of date
 rand^0.80.10.0out of date
 raw-window-handle^0.50.6.2out of date
 serde^1.01.0.228up to date
 serde_repr^0.10.1.20up to date
 tokio ⚠️^1.211.50.0maybe insecure
 tracing^0.10.1.44up to date
 url^2.32.5.8up to date
 wayland-backend^0.10.3.14out of date
 wayland-client^0.300.31.13out of date
 wayland-protocols^0.300.32.11out of date
 zbus^3.15.14.0out of date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 byteorder^1.41.5.0up to date
 serde_json^1.01.0.149up 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);