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 leo3 Dependencies (2 total, 1 possibly insecure)
Crate Required Latest Status paste ^1.01.0.15up to date tokio ⚠️ ^11.50.0maybe insecure
Dev dependencies (3 total, 1 possibly insecure)
Crate Required Latest Status trybuild ^1.01.0.116up to date futures ^0.30.3.32up to date tokio ⚠️ ^11.50.0maybe insecure
Crate leo3-ffi No external dependencies! 🙌
Crate leo3-build-config No external dependencies! 🙌
Crate leo3-macros Dependencies (3 total, all up-to-date)
Crate Required Latest Status proc-macro2 ^1.01.0.106up to date quote ^1.01.0.45up to date syn ^2.02.0.117up to date
Crate leo3-macros-backend Dependencies (3 total, all up-to-date)
Crate Required Latest Status proc-macro2 ^1.01.0.106up to date quote ^1.01.0.45up to date syn ^2.02.0.117up to date
Security Vulnerabilities tokio: reject_remote_clients Configuration corruptionRUSTSEC-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);
Patched
>=1.18.4, <1.19.0
>=1.20.3, <1.21.0
>=1.23.1