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, 8 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-fs^2.1.02.2.0up to date
 async-net^2.0.02.0.0up to date
 enumflags2^0.70.7.12up to date
 futures-channel^0.30.3.31up to date
 futures-util^0.30.3.31up to date
 gdk4-wayland^0.80.10.1out of date
 gdk4-x11^0.80.10.1out of date
 glib^0.190.21.2out of date
 gtk4^0.80.10.1out of date
 pipewire^0.80.9.2out of date
 rand^0.80.9.2out of date
 raw-window-handle^0.60.6.2up to date
 serde^1.01.0.225up to date
 serde_repr^0.10.1.20up to date
 tokio ⚠️^1.211.47.1maybe insecure
 tracing^0.10.1.41up to date
 url^2.32.5.7up to date
 wayland-backend^0.30.3.11up to date
 wayland-client^0.310.31.11up to date
 wayland-protocols^0.310.32.9out of date
 zbus^4.05.11.0out of date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 serde_json^1.01.0.145up 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);