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 facet-json

Dependencies

(17 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 axum-core^0.50.5.6up to date
 corosensei^0.30.3.3up to date
 facet^0.43.20.44.3out of date
 facet-core^0.43.20.44.3out of date
 facet-format^0.43.20.44.5out of date
 facet-reflect^0.43.20.44.3out of date
 futures-io^0.30.3.32up to date
 http^1.4.01.4.0up to date
 http-body-util^0.10.1.3up to date
 itoa^11.0.18up to date
 lexical-parse-float^1.0.51.0.6up to date
 lexical-parse-integer^1.0.51.0.6up to date
 memchr^22.8.0up to date
 mime^0.30.3.17up to date
 tokio ⚠️^11.50.0maybe insecure
 tracing^0.1.430.1.44up to date
 zmij^11.0.21up to date

Dev dependencies

(8 total, 1 possibly insecure)

CrateRequiredLatestStatus
 compact_str^0.9.00.9.0up to date
 indoc^2.0.72.0.7up to date
 libtest-mimic^0.8.10.8.2up to date
 serde_json^1.0.1451.0.149up to date
 smol_str^0.3.40.3.6up to date
 tendril^0.5.00.5.0up to date
 tokio ⚠️^11.50.0maybe insecure
 tracing^0.1.430.1.44up to date

Security Vulnerabilities

tokio: reject_remote_clients Configuration corruption

RUSTSEC-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);