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 rocket
Dependencies (38 total, 1 possibly insecure)
Dev dependencies (3 total, 1 possibly insecure)
Build dependencies (1 total, all up-to-date)
Crate rocket_codegen
Dependencies (8 total, all up-to-date)
Dev dependencies (4 total, all up-to-date)
Crate rocket_http
Dependencies (14 total, all up-to-date)
Crate rocket_db_pools_codegen
Dependencies (2 total, all up-to-date)
Crate Required Latest Status devise ^0.4
0.4.1
up to date quote ^1
1.0.36
up to date
Dev dependencies (2 total, all up-to-date)
Crate rocket_db_pools
Dependencies (7 total, 3 outdated)
Build dependencies (1 total, all up-to-date)
Crate rocket_sync_db_pools_codegen
Dependencies (2 total, all up-to-date)
Crate Required Latest Status quote ^1.0
1.0.36
up to date devise ^0.4
0.4.1
up to date
Dev dependencies (2 total, all up-to-date)
Crate rocket_sync_db_pools
Dependencies (10 total, 3 outdated, 1 possibly insecure)
Build dependencies (1 total, all up-to-date)
Crate rocket_dyn_templates
Dependencies (6 total, all up-to-date)
Dev dependencies (1 total, all up-to-date)
Crate rocket_ws
Dependencies (1 total, all up-to-date)
Crate rocket_docs_tests
Dev dependencies (3 total, 1 possibly insecure)
Crate Required Latest Status figment ^0.10.17
0.10.18
up to date tokio ⚠️ ^1
1.37.0
maybe insecure rand ^0.8
0.8.5
up 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
rustls
: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network inputRUSTSEC-2024-0336
If a close_notify
alert is received during a handshake, complete_io
does not terminate.
Callers which do not call complete_io
are not affected.
rustls-tokio
and rustls-ffi
do not call complete_io
and are not affected.
rustls::Stream
and rustls::StreamOwned
types use
complete_io
and are affected.
Patched
>=0.23.5
>=0.22.4, <0.23.0
>=0.21.11, <0.22.0