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 socketcan

Dependencies

(20 total, 7 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.100up to date
 async-io^1.132.6.0out of date
 async-std^1.121.13.2up to date
 bitflags^2.62.9.4up to date
 clap^3.24.5.48out of date
 embedded-can^0.40.4.1up to date
 futures^0.30.3.31up to date
 hex^0.40.4.3up to date
 itertools^0.130.14.0out of date
 libc^0.20.2.176up to date
 libudev^0.30.3.0up to date
 log^0.40.4.28up to date
 mio^11.0.4up to date
 nb^11.1.0up to date
 neli^0.60.7.1out of date
 nix^0.290.30.1out of date
 smol^1.32.0.2out of date
 socket2^0.50.6.0out of date
 thiserror^22.0.16up to date
 tokio ⚠️^11.47.1maybe insecure

Dev dependencies

(10 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.100up to date
 async-std^1.121.13.2up to date
 clap^3.24.5.48out of date
 ctrlc^3.2.23.5.0up to date
 futures^0.30.3.31up to date
 futures-timer^0.33.0.3out of date
 futures-util^0.30.3.31up to date
 nb^1.01.1.0up to date
 serial_test^2.03.2.0out of date
 tokio ⚠️^11.47.1maybe insecure

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);