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 srs2dge
Dev dependencies (8 total, 4 outdated)
Crate srs2dge-link-static
No external dependencies! 🙌
Crate srs2dge-link-dynamic
No external dependencies! 🙌
Crate srs2dge-core
Dependencies (18 total, 8 outdated, 1 possibly insecure)
Crate srs2dge-ecs
Dependencies (3 total, all up-to-date)
Crate srs2dge-gizmos
No external dependencies! 🙌
Crate srs2dge-gui
No external dependencies! 🙌
Crate srs2dge-gui-derive
Dependencies (4 total, 2 outdated)
Crate Required Latest Status darling ^0.14.1
0.20.11
out of date proc-macro2 ^1.0.42
1.0.95
up to date quote ^1.0.20
1.0.40
up to date syn ^1.0.98
2.0.101
out of date
Crate srs2dge-presets
Dependencies (1 total, all up-to-date)
Crate Required Latest Status bytemuck ^1.9
1.23.0
up to date
Crate srs2dge-res
No external dependencies! 🙌
Crate srs2dge-text
Dependencies (4 total, 2 outdated)
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