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 tauri
Dependencies (41 total, 9 outdated, 1 possibly insecure)
Dev dependencies (10 total, 3 outdated, 1 possibly insecure)
Build dependencies (2 total, all up-to-date)
Crate Required Latest Status heck ^0.4
0.4.1
up to date once_cell ^1
1.17.1
up to date
Crate tauri-runtime
Dependencies (9 total, 1 outdated)
Crate tauri-runtime-wry
Dependencies (4 total, 2 outdated)
Crate tauri-macros
Dependencies (4 total, 1 outdated)
Crate Required Latest Status proc-macro2 ^1
1.0.53
up to date quote ^1
1.0.26
up to date syn ^1
2.0.10
out of date heck ^0.4
0.4.1
up to date
Crate tauri-utils
Dependencies (24 total, 5 outdated)
Crate tauri-build
Dependencies (9 total, 1 outdated)
Crate tauri-codegen
Dependencies (15 total, all up-to-date)
Crate config-schema
Build dependencies (5 total, 1 outdated)
Crate restart
Dev dependencies (1 total, all up-to-date)
Crate Required Latest Status tempfile ^3
3.4.0
up to date
Crate app-updater
Dependencies (4 total, 2 outdated)
Crate Required Latest Status serde ^1
1.0.158
up to date serde_json ^1
1.0.94
up to date tiny_http ^0.11
0.12.0
out of date time =0.3.15
0.3.20
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