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 lurk

Dependencies

(33 total, all up-to-date)

CrateRequiredLatestStatus
 base32ct^0.2.00.2.0up to date
 base-x^0.2.110.2.11up to date
 bytecount^0.6.70.6.8up to date
 config^0.14.00.14.0up to date
 dashmap^5.5.05.5.3up to date
 fxhash^0.2.10.2.1up to date
 generic-array^1.01.0.0up to date
 hex^0.4.30.4.3up to date
 indexmap^2.1.02.2.6up to date
 itertools^0.120.12.1up to date
 match_opt^0.1.20.1.2up to date
 nom^7.1.37.1.3up to date
 nom_locate^4.1.04.2.0up to date
 num-bigint^0.4.30.4.5up to date
 num_cpus^1.10.11.16.0up to date
 num-integer^0.1.450.1.46up to date
 num-traits^0.2.150.2.19up to date
 rand_core^0.6.40.6.4up to date
 rand_xorshift^0.3.00.3.0up to date
 rayon^1.7.01.10.0up to date
 rustyline-derive^0.100.10.0up to date
 serde_bytes^0.11.120.11.14up to date
 serde_repr^0.1.140.1.19up to date
 strum^0.260.26.2up to date
 tap^1.0.11.0.1up to date
 stable_deref_trait^1.2.01.2.0up to date
 abomonation_derive_ng^0.1.00.1.0up to date
 byteorder^1.4.31.5.0up to date
 sha2^0.10.20.10.8up to date
 reqwest^0.12.20.12.4up to date
 ansi_term^0.12.10.12.1up to date
 arc-swap^1.6.01.7.1up to date
 halo2curves^0.6.00.6.1up to date

Dev dependencies

(9 total, all up-to-date)

CrateRequiredLatestStatus
 assert_cmd^2.0.122.0.14up to date
 cfg-if^1.0.01.0.0up to date
 ascii_table^4.0.24.0.3up to date
 criterion^0.50.5.1up to date
 expect-test^1.4.11.5.0up to date
 hex^0.4.30.4.3up to date
 statrs^0.16.00.16.0up to date
 tiny-keccak^2.0.22.0.2up to date
 tap^1.0.11.0.1up to date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 vergen^88.3.1up to date

Crate lurk-macros

Dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 proc-macro2^1.0.661.0.82up to date
 quote^1.0.311.0.36up to date
 syn^1.0.1092.0.63out of date

Crate lurk-metrics

Dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 hdrhistogram^7.5.27.5.4up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 regex^1.9.41.10.4up to date
 tracing-test^0.20.2.4up to date

Crate foil

Dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 indexmap^2.2.32.2.6up to date
 generic-array^0.14.71.0.0out of date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 env_logger*0.11.3up to date
 test-log^0.2.120.2.16up to date

Crate chain-server

Dependencies

(5 total, 1 possibly insecure)

CrateRequiredLatestStatus
 halo2curves^0.6.00.6.1up to date
 prost^0.120.12.4up to date
 rustyline^14.014.0.0up to date
 tokio ⚠️^1.01.37.0maybe insecure
 tonic^0.110.11.0up to date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 tonic-build^0.110.11.0up 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);