Deps.rs

tracing-opentelemetry-setup 0.8.7

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-setup

Dependencies

(18 total, 2 possibly insecure)

CrateRequiredLatestStatus
 http^11.5.0up to date
 metrics-opentelemetry^0.24032.50.24032.9up to date
 opentelemetry^0.320.32.0up to date
 opentelemetry-appender-tracing^0.320.32.0up to date
 opentelemetry-datadog^0.200.20.1up to date
 opentelemetry-http^0.320.32.0up to date
 opentelemetry-otlp^0.320.32.0up to date
 opentelemetry_sdk^0.320.32.1up to date
 serde^11.0.229up to date
 serde_json^11.0.151up to date
 str-buf^44.0.0up to date
 time ⚠️^0.30.3.55maybe insecure
 tokio ⚠️^1.221.53.1maybe insecure
 tonic^0.140.14.6up to date
 tracing^0.10.1.44up to date
 tracing-opentelemetry^0.330.33.0up to date
 tracing-subscriber^0.3.220.3.23up to date
 ureq^33.4.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);

time: Denial of Service via Stack Exhaustion

RUSTSEC-2026-0009

Impact

When user-provided input is provided to any type that parses with the RFC 2822 format, a denial of service attack via stack exhaustion is possible. The attack relies on formally deprecated and rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary, non-malicious input will never encounter this scenario.

Patches

A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned rather than exhausting the stack.

Workarounds

Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of the stack consumed would be at most a factor of the length of the input.