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.
algorithmia(11 total, 5 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| backtrace | ^0.3 | 0.3.75 | up to date |
| base64 | ^0.10.1 | 0.22.1 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.41 | maybe insecure |
| headers-ext | ^0.0.4 | 0.0.4 | up to date |
| http ⚠️ | ^0.1.15 | 1.3.1 | out of date |
| hyper ⚠️ | ^0.12 | 1.6.0 | out of date |
| mime | ^0.3.13 | 0.3.17 | up to date |
| reqwest | ^0.9.6 | 0.12.22 | out of date |
| serde | ^1.0 | 1.0.219 | up to date |
| serde_json | ^1.0 | 1.0.140 | up to date |
| url | ^1.7 | 2.5.4 | out of date |
http: Integer Overflow in HeaderMap::reserve() can cause Denial of ServiceHeaderMap::reserve() used usize::next_power_of_two() to calculate the increased capacity.
However, next_power_of_two() silently overflows to 0 if given a sufficiently large number
in release mode.
If the map was not empty when the overflow happens,
the library will invoke self.grow(0) and start infinite probing.
This allows an attacker who controls the argument to reserve()
to cause a potential denial of service (DoS).
The flaw was corrected in 0.1.20 release of http crate.
http: HeaderMap::Drain API is unsoundAffected versions of this crate incorrectly used raw pointer, which introduced unsoundness in its public safe API.
Failing to drop the Drain struct causes double-free, and it is possible to violate Rust's alias rule and cause data race with Drain's Iterator implementation.
The flaw was corrected in 0.1.20 release of http crate.
chrono: Potential segfault in `localtime_r` invocationsUnix-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.
No workarounds are known.
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.