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 attohttpc

Dependencies

(17 total, 1 possibly insecure)

CrateRequiredLatestStatus
 encoding_rs^0.80.8.29up to date
 encoding_rs_io^0.10.1.7up to date
 flate2^1.01.0.22up to date
 http^0.20.2.5up to date
 log^0.40.4.14up to date
 mime^0.30.3.16up to date
 multipart^0.180.18.0up to date
 native-tls^0.20.2.8up to date
 rustls^0.200.20.2up to date
 serde^11.0.130up to date
 serde_json^11.0.72up to date
 serde_urlencoded^0.70.7.0up to date
 url^22.2.2up to date
 webpki^0.220.22.0up to date
 webpki-roots^0.220.22.1up to date
 wildmatch^22.1.0up to date
 openssl ⚠️^0.100.10.38maybe insecure

Dev dependencies

(9 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.51up to date
 env_logger^0.90.9.0up to date
 futures^0.30.3.18up to date
 futures-util^0.30.3.18up to date
 hyper ⚠️^0.140.14.15maybe insecure
 tokio ⚠️^11.14.0maybe insecure
 tokio-rustls^0.220.23.1out of date
 tokio-stream^0.10.1.8up to date
 warp^0.30.3.2up to date

Security Vulnerabilities

openssl: Use after free in CMS Signing

RUSTSEC-2018-0010

Affected versions of the OpenSSL crate used structures after they'd been freed.

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: Data race when sending and receiving after closing a `oneshot` channel

RUSTSEC-2021-0124

If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv.

When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.

Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.

See tokio#4225 for more details.