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 fuzz No external dependencies! 🙌
Crate neqo-bin Dependencies (5 total, 1 possibly insecure)
Dev dependencies (2 total, 1 possibly insecure)
Crate Required Latest Status criterion ^0.50.5.1up to date tokio ⚠️ ^11.41.1maybe insecure
Crate neqo-common Dependencies (2 total, 1 outdated)
Crate Required Latest Status env_logger ^0.100.11.5out of date hex ^0.40.4.3up to date
Dev dependencies (1 total, all up-to-date)
Crate Required Latest Status criterion ^0.50.5.1up to date
Crate neqo-crypto Build dependencies (6 total, 2 outdated)
Crate neqo-http3 Dependencies (2 total, all up-to-date)
Crate Required Latest Status enumset ^1.11.1.5up to date sfv ^0.90.9.4up to date
Crate neqo-qpack No external dependencies! 🙌
Crate neqo-transport Dependencies (2 total, all up-to-date)
Crate Required Latest Status indexmap ^2.22.7.0up to date smallvec ^1.131.13.2up to date
Dev dependencies (1 total, all up-to-date)
Crate Required Latest Status criterion ^0.50.5.1up to date
Crate neqo-udp No external dependencies! 🙌
Crate test-fixture No external dependencies! 🙌
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
