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

Dependencies

(27 total, 13 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-std^1.10.01.12.0up to date
 async-trait^0.10.1.80up to date
 base64^0.21.00.22.1out of date
 futures-core^0.30.3.30up to date
 futures-executor^0.30.3.30up to date
 futures-util^0.30.3.30up to date
 headers^0.3.20.4.0out of date
 http^0.21.1.0out of date
 hyper ⚠️^0.141.3.1out of date
 hyper-tls^0.5.00.6.0out of date
 isahc^1.41.7.2up to date
 js-sys^0.30.3.69up to date
 opentelemetry^0.210.23.0out of date
 opentelemetry-http^0.100.12.0out of date
 opentelemetry-semantic-conventions^0.130.15.0out of date
 opentelemetry_sdk^0.210.23.0out of date
 pin-project-lite^0.20.2.14up to date
 prost^0.11.60.12.6out of date
 prost-types^0.11.60.12.6out of date
 reqwest^0.110.12.4out of date
 surf^2.02.3.2up to date
 thrift^0.17.00.17.0up to date
 tokio ⚠️^1.01.37.0maybe insecure
 tonic^0.9.00.11.0out of date
 wasm-bindgen^0.20.2.92up to date
 wasm-bindgen-futures^0.4.180.4.42up to date
 web-sys^0.3.40.3.69up to date

Dev dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^11.6.0up to date
 futures-executor^0.30.3.30up to date
 tokio ⚠️^1.01.37.0maybe insecure

Security Vulnerabilities

hyper: Lenient `hyper` header parsing of `Content-Length` could allow request smuggling

RUSTSEC-2021-0078

hyper's HTTP header parser accepted, according to RFC 7230, illegal contents inside Content-Length headers. Due to this, upstream HTTP proxies that ignore the header may still forward them along if it chooses to ignore the error.

To be vulnerable, hyper must be used as an HTTP/1 server and using an HTTP proxy upstream that ignores the header's contents but still forwards it. Due to all the factors that must line up, an attack exploiting this vulnerability is unlikely.

hyper: Integer overflow in `hyper`'s parsing of the `Transfer-Encoding` header leads to data loss

RUSTSEC-2021-0079

When decoding chunk sizes that are too large, hyper's code would encounter an integer overflow. Depending on the situation, this could lead to data loss from an incorrect total size, or in rarer cases, a request smuggling attack.

To be vulnerable, you must be using hyper for any HTTP/1 purpose, including as a client or server, and consumers must send requests or responses that specify a chunk size greater than 18 exabytes. For a possible request smuggling attack to be possible, any upstream proxies must accept a chunk size greater than 64 bits.

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