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 jsonschema

Dependencies

(19 total, 1 possibly insecure)

CrateRequiredLatestStatus
 ahash^0.80.8.11up to date
 async-trait^0.1.860.1.87up to date
 base64^0.220.22.1up to date
 bytecount^0.60.6.8up to date
 email_address^0.2.90.2.9up to date
 fancy-regex^0.140.14.0up to date
 fraction^0.150.15.3up to date
 idna^1.0.21.0.3up to date
 itoa^11.0.15up to date
 num-cmp^0.10.1.0up to date
 once_cell^1.20.11.21.0up to date
 percent-encoding^2.32.3.1up to date
 referencing^0.29.00.29.0up to date
 regex-syntax^0.8.50.8.5up to date
 reqwest^0.120.12.12up to date
 serde^1.01.0.219up to date
 serde_json^11.0.140up to date
 tokio ⚠️^1.01.44.0maybe insecure
 uuid-simd^0.80.8.0up to date

Dev dependencies

(6 total, 1 possibly insecure)

CrateRequiredLatestStatus
 codspeed-criterion-compat^2.72.9.1up to date
 criterion^0.50.5.1up to date
 mockito^1.51.7.0up to date
 tempfile^3.13.03.18.0up to date
 test-case^33.3.1up to date
 tokio ⚠️^11.44.0maybe insecure

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