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 gitpad
Dependencies (27 total, 8 outdated, 1 possibly insecure)
Dev dependencies (1 total, all up-to-date)
Crate Required Latest Status actix-rt ^2
2.9.0
up to date
Build dependencies (2 total, all up-to-date)
Crate Required Latest Status mime ^0.3.16
0.3.17
up to date serde_json ^1
1.0.116
up to date
Crate db-core
Dependencies (3 total, all up-to-date)
Dev dependencies (1 total, all up-to-date)
Crate Required Latest Status serde_json ^1
1.0.116
up to date
Crate db-sqlx-postgres
Dependencies (2 total, 1 outdated)
Crate Required Latest Status sqlx ^0.5.10
0.7.4
out of date async-trait ^0.1.51
0.1.80
up to date
Dev dependencies (2 total, 1 outdated)
Crate Required Latest Status actix-rt ^2
2.9.0
up to date sqlx ^0.5.10
0.7.4
out of date
Crate db-sqlx-sqlite
Dependencies (2 total, 1 outdated)
Crate Required Latest Status sqlx ^0.5.10
0.7.4
out of date async-trait ^0.1.51
0.1.80
up to date
Dev dependencies (2 total, 1 outdated)
Crate Required Latest Status actix-rt ^2
2.9.0
up to date sqlx ^0.5.10
0.7.4
out of 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