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

(24 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 ahash^0.80.8.12up to date
 async-trait^0.1.860.1.89up to date
 bytecount^0.60.6.9up to date
 data-encoding^2.92.10.0up to date
 email_address^0.2.90.2.9up to date
 fancy-regex^0.170.17.0up to date
 fraction^0.150.15.3up to date
 getrandom^0.3.40.4.1out of date
 idna^1.0.21.1.0up to date
 itoa^11.0.17up to date
 num-bigint^0.40.4.6up to date
 num-cmp^0.10.1.0up to date
 num-traits^0.2.190.2.19up to date
 percent-encoding^2.32.3.2up to date
 referencing^0.40.20.41.0out of date
 regex^1.11.11.12.3up to date
 regex-syntax^0.8.50.8.9up to date
 reqwest^0.130.13.2up to date
 rustls ⚠️^0.230.23.36maybe insecure
 serde^1.01.0.228up to date
 serde_json^11.0.149up to date
 tokio ⚠️^1.01.49.0maybe insecure
 unicode-general-category^1.11.1.0up to date
 uuid-simd^0.80.8.0up to date

Dev dependencies

(7 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 codspeed-criterion-compat^4.14.3.0up to date
 criterion^0.70.8.2out of date
 futures^0.30.3.31up to date
 tempfile^3.13.03.24.0up to date
 test-case^33.3.1up to date
 tokio ⚠️^11.49.0maybe insecure
 wasm-bindgen-test^0.3.550.3.58up 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);

rustls: rustls network-reachable panic in `Acceptor::accept`

RUSTSEC-2024-0399

A bug introduced in rustls 0.23.13 leads to a panic if the received TLS ClientHello is fragmented. Only servers that use rustls::server::Acceptor::accept() are affected.

Servers that use tokio-rustls's LazyConfigAcceptor API are affected.

Servers that use tokio-rustls's TlsAcceptor API are not affected.

Servers that use rustls-ffi's rustls_acceptor_accept API are affected.