This project contains known security vulnerabilities. Find detailed information at the bottom.
oha(23 total, 15 outdated, 1 insecure, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1 | 1.0.82 | up to date |
| average | ^0.10.4 | 0.15.0 | out of date |
| base64 | ^0.12.0 | 0.22.0 | out of date |
| byte-unit | ^3.0.3 | 5.1.4 | out of date |
| clap | ^2 | 4.5.4 | out of date |
| crossbeam | ^0.7 | 0.8.4 | out of date |
| crossterm | ^0.14.0 | 0.27.0 | out of date |
| float-ord | ^0.2.0 | 0.3.2 | out of date |
| flume | ^0.7.0 | 0.11.0 | out of date |
| futures | ^0.3 | 0.3.30 | up to date |
| futures-util | ^0.3.4 | 0.3.30 | up to date |
| http | ^0.2 | 1.1.0 | out of date |
| hyper ⚠️ | ^0.13.4 | 1.3.1 | out of date |
| libc | ^0.2.67 | 0.2.153 | up to date |
| native-tls | ^0.2.4 | 0.2.11 | up to date |
| parse_duration ⚠️ | ^2 | 2.1.1 | insecure |
| rand | ^0.7 | 0.8.5 | out of date |
| rlimit | ^0.3.0 | 0.10.1 | out of date |
| structopt | ^0.3 | 0.3.26 | up to date |
| tokio ⚠️ | ^0.2 | 1.37.0 | out of date |
| tokio-tls | ^0.3.0 | 0.3.1 | up to date |
| trust-dns-resolver | ^0.19.3 | 0.23.2 | out of date |
| tui | ^0.8.0 | 0.19.0 | out of date |
(6 total, 5 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| assert_cmd | ^1.0.0 | 2.0.14 | out of date |
| bytes | ^0.5.4 | 1.6.0 | out of date |
| get-port | ^1.3.1 | 4.0.0 | out of date |
| http | ^0.2 | 1.1.0 | out of date |
| lazy_static | ^1.4.0 | 1.4.0 | up to date |
| warp ⚠️ | ^0.2 | 0.3.7 | out of date |
parse_duration: Denial of service through parsing payloads with too big exponentThe parse_duration::parse function allows for parsing duration strings with exponents like 5e5s where under the hood, the BigInt type along with the pow function are used for such payloads. Passing an arbitrarily big exponent makes the parse_duration::parse function to process the payload for a very long time taking up CPU and memory.
This allows an attacker to cause a DoS if the parse_duration::parse function is used to process untrusted input.
hyper: Lenient `hyper` header parsing of `Content-Length` could allow request smugglinghyper'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 lossWhen 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` channelIf 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.
warp: Improper validation of Windows paths could lead to directory traversal attackPath resolution in warp::filters::fs::dir didn't correctly validate Windows paths
meaning paths like /foo/bar/c:/windows/web/screen/img101.png would be allowed
and respond with the contents of c:/windows/web/screen/img101.png. Thus users
could potentially read files anywhere on the filesystem.
This only impacts Windows. Linux and other unix likes are not impacted by this.