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.
tiny_http(9 total, 2 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| ascii | ^1.0 | 1.1.0 | up to date |
| chunked_transfer | ^1 | 1.5.0 | up to date |
| log | ^0.4 | 0.4.29 | up to date |
| openssl ⚠️ | ^0.10 | 0.10.76 | maybe insecure |
| rustls ⚠️ | ^0.20 | 0.23.37 | out of date |
| rustls-pemfile | ^0.2.1 | 2.2.0 | out of date |
| time ⚠️ | ^0.3 | 0.3.47 | maybe insecure |
| url | ^2 | 2.5.8 | up to date |
| zeroize | ^1.5.2 | 1.8.2 | up to date |
(3 total, 2 outdated, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| fdlimit | ^0.1 | 0.3.0 | out of date |
| rustc-serialize ⚠️ | ^0.3 | 0.3.25 | insecure |
| sha1 | ^0.6.0 | 0.11.0 | out of date |
rustc-serialize: Stack overflow in rustc_serialize when parsing deeply nested JSONWhen parsing JSON using json::Json::from_str, there is no limit to the depth of the stack, therefore deeply nested objects can cause a stack overflow, which aborts the process.
Example code that triggers the vulnerability is
fn main() {
let _ = rustc_serialize::json::Json::from_str(&"[0,[".repeat(10000));
}
serde is recommended as a replacement to rustc_serialize.
rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network inputIf a close_notify alert is received during a handshake, complete_io
does not terminate.
Callers which do not call complete_io are not affected.
rustls-tokio and rustls-ffi do not call complete_io
and are not affected.
rustls::Stream and rustls::StreamOwned types use
complete_io and are affected.
openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.
In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).
The maintainers thank quitbug for reporting this vulnerability to us.
time: Denial of Service via Stack ExhaustionWhen user-provided input is provided to any type that parses with the RFC 2822 format, a denial of service attack via stack exhaustion is possible. The attack relies on formally deprecated and rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary, non-malicious input will never encounter this scenario.
A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned rather than exhausting the stack.
Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of the stack consumed would be at most a factor of the length of the input.