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 web-example

Dependencies

(6 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.98up to date
 axum^0.70.8.4out of date
 axum-extra^0.90.10.1out of date
 serde^11.0.219up to date
 tokio ⚠️^11.46.1maybe insecure
 tower-http^0.60.6.6up to date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 anyhow^11.0.98up to date

Crate variant-config

Dependencies

(12 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 ahash^0.80.8.12up to date
 anyhow^11.0.98up to date
 cranelift^0.1110.121.1out of date
 cranelift-jit^0.1110.121.1out of date
 cranelift-module^0.1110.121.1out of date
 hashbrown ⚠️^0.150.15.4maybe insecure
 log^0.40.4.27up to date
 peg^0.80.8.5up to date
 serde^11.0.219up to date
 serde_json^11.0.140up to date
 serde_yaml^0.90.9.34+deprecatedup to date
 toml^0.80.8.23up to date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 criterion^0.50.6.0out of date

Crate api

Dependencies

(5 total, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.98up to date
 reqwest^0.120.12.22up to date
 serde^11.0.219up to date
 tokio ⚠️^11.46.1maybe insecure
 vercel_runtime^11.1.6up 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);

hashbrown: Borsh serialization of HashMap is non-canonical

RUSTSEC-2024-0402

The borsh serialization of the HashMap did not follow the borsh specification. It potentially produced non-canonical encodings dependent on insertion order. It also did not perform canonicty checks on decoding.

This can result in consensus splits and cause equivalent objects to be considered distinct.

This was patched in 0.15.1.