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 enigo

Dependencies

(20 total, 1 possibly insecure)

CrateRequiredLatestStatus
 log^0.40.4.27up to date
 serde^11.0.219up to date
 windows^0.610.61.1up to date
 core-foundation^0.100.10.0up to date
 core-graphics^0.240.24.0up to date
 objc2^0.60.6.1up to date
 objc2-app-kit^0.30.3.1up to date
 objc2-foundation^0.30.3.1up to date
 foreign-types-shared^0.30.3.1up to date
 libc^0.20.2.172up to date
 reis^0.50.5.0up to date
 ashpd^0.110.11.0up to date
 tokio ⚠️^11.44.2maybe insecure
 wayland-protocols-misc^0.30.3.8up to date
 wayland-protocols-wlr^0.30.3.8up to date
 wayland-client^0.310.31.10up to date
 x11rb^0.130.13.1up to date
 xkbcommon^0.80.8.0up to date
 xkeysym^0.20.2.1up to date
 tempfile^33.19.1up to date

Dev dependencies

(10 total, all up-to-date)

CrateRequiredLatestStatus
 env_logger^0.110.11.8up to date
 serde^11.0.219up to date
 tungstenite^0.260.26.2up to date
 url^22.5.4up to date
 webbrowser^1.01.0.4up to date
 ron^0.100.10.1up to date
 strum^0.270.27.1up to date
 strum_macros^0.270.27.1up to date
 rdev^0.50.5.3up to date
 mouse_position^0.10.1.4up 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);