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 near-o11y

Dependencies

(18 total, 11 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 actix^0.13.00.13.5up to date
 atty^0.20.2.14up to date
 clap^3.1.64.5.40out of date
 near-crypto^0.16.10.30.1out of date
 near-primitives-core^0.16.10.30.1out of date
 once_cell^1.13.11.21.3up to date
 opentelemetry^0.17.00.30.0out of date
 opentelemetry-otlp^0.10.00.30.0out of date
 opentelemetry-semantic-conventions^0.9.00.30.0out of date
 prometheus^0.13.10.14.0out of date
 serde^1.0.1361.0.219up to date
 strum^0.240.27.1out of date
 thiserror^1.0.302.0.12out of date
 tokio ⚠️~1.191.45.1out of date
 tracing^0.1.360.1.41up to date
 tracing-appender^0.2.20.2.3up to date
 tracing-opentelemetry^0.17.00.31.0out of date
 tracing-subscriber^0.3.150.3.19up to date

Dev dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 bencher^0.1.50.1.5up to date
 itoa^1.01.0.15up to date
 smartstring^1.0.11.0.1up 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);