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

CrateRequiredLatestStatus
 async-fs^2.1.02.1.2up to date
 async-net^2.0.02.0.0up to date
 enumflags2^0.70.7.9up to date
 futures-channel^0.30.3.30up to date
 futures-util^0.30.3.30up to date
 gdk4-wayland^0.80.8.2up to date
 gdk4-x11^0.80.8.2up to date
 glib^0.190.19.6up to date
 gtk4^0.80.8.2up to date
 pipewire^0.80.8.0up to date
 rand^0.80.8.5up to date
 raw-window-handle^0.60.6.1up to date
 serde^1.01.0.201up to date
 serde_repr^0.10.1.19up to date
 tokio ⚠️^1.211.37.0maybe insecure
 tracing^0.10.1.40up to date
 url^2.32.5.0up to date
 wayland-backend^0.30.3.3up to date
 wayland-client^0.310.31.2up to date
 wayland-protocols^0.310.31.2up to date
 zbus^4.04.2.1up to date

Dev dependencies

(1 total, all up-to-date)

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