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 tracing-opentelemetry

Dependencies

(12 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.560.1.80up to date
 js-sys^0.3.640.3.69up to date
 once_cell^1.13.01.19.0up to date
 opentelemetry^0.21.00.22.0out of date
 opentelemetry_sdk^0.21.00.22.1out of date
 smallvec ⚠️^1.01.13.2maybe insecure
 thiserror^1.0.311.0.59up to date
 tracing^0.1.350.1.40up to date
 tracing-core^0.1.280.1.32up to date
 tracing-log^0.2.00.2.0up to date
 tracing-subscriber^0.3.00.3.18up to date
 web-time^0.2.01.1.0out of date

Dev dependencies

(14 total, 6 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait^0.1.560.1.80up to date
 criterion^0.5.10.5.1up to date
 futures-util^0.30.3.30up to date
 opentelemetry^0.21.00.22.0out of date
 opentelemetry-jaeger^0.20.00.21.0out of date
 opentelemetry-otlp^0.14.00.15.0out of date
 opentelemetry-semantic-conventions^0.13.00.14.0out of date
 opentelemetry-stdout^0.2.00.3.0out of date
 opentelemetry_sdk^0.21.00.22.1out of date
 pprof^0.13.00.13.0up to date
 tokio ⚠️^11.37.0maybe insecure
 tokio-stream^0.10.1.15up to date
 tracing^0.1.350.1.40up to date
 tracing-subscriber^0.3.00.3.18up to date

Security Vulnerabilities

smallvec: Buffer overflow in SmallVec::insert_many

RUSTSEC-2021-0003

A bug in the SmallVec::insert_many method caused it to allocate a buffer that was smaller than needed. It then wrote past the end of the buffer, causing a buffer overflow and memory corruption on the heap.

This bug was only triggered if the iterator passed to insert_many yielded more items than the lower bound returned from its size_hint method.

The flaw was corrected in smallvec 0.6.14 and 1.6.1, by ensuring that additional space is always reserved for each item inserted. The fix also simplified the implementation of insert_many to use less unsafe code, so it is easier to verify its correctness.

Thank you to Yechan Bae (@Qwaz) and the Rust group at Georgia Tech’s SSLab for finding and reporting this bug.

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