This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate trade

Dependencies

(20 total, 11 outdated, 1 insecure, 4 possibly insecure)

CrateRequiredLatestStatus
 arrayvec^0.40.7.4out of date
 base64^0.90.22.0out of date
 bitflags^12.5.0out of date
 chashmap^2.2.02.2.2up to date
 chrono ⚠️^0.40.4.37maybe insecure
 env_logger^0.50.11.3out of date
 failure^0.10.1.8up to date
 failure_derive^0.10.1.8up to date
 futures^0.10.3.30out of date
 hex^0.30.4.3out of date
 hyper ⚠️^0.121.2.0out of date
 hyper-tls^0.30.6.0out of date
 log^0.40.4.21up to date
 openssl ⚠️^0.100.10.64maybe insecure
 serde^11.0.197up to date
 serde_derive^11.0.197up to date
 serde_json^11.0.115up to date
 tokio ⚠️^0.11.36.0out of date
 uuid^0.61.8.0out of date
 ws ⚠️^0.70.9.2insecure

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 criterion^0.20.5.1out of date

Security Vulnerabilities

ws: Insufficient size checks in outgoing buffer in ws allows remote attacker to run the process out of memory

RUSTSEC-2020-0043

Affected versions of this crate did not properly check and cap the growth of the outgoing buffer.

This allows a remote attacker to take down the process by growing the buffer of their (single) connection until the process runs out of memory it can allocate and is killed.

The flaw was corrected in the parity-ws fork (>=0.10.0) by disconnecting a client when the buffer runs full.

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

Workarounds

No workarounds are known.

References

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.

openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-read

RUSTSEC-2023-0044

When this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.