This project contains known security vulnerabilities. Find detailed information at the bottom.
tiny_http(8 total, 2 outdated, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| ascii | ^1.0 | 1.1.0 | up to date |
| chunked_transfer | ^1 | 1.5.0 | up to date |
| httpdate | ^1.0.2 | 1.0.3 | up to date |
| log | ^0.4.4 | 0.4.34 | up to date |
| openssl | ^0.10 | 0.10.81 | up to date |
| rustls ⚠️ | ^0.20 | 0.23.45 | insecure |
| rustls-pemfile | ^0.2.1 | 2.2.0 | out of date |
| zeroize | ^1 | 1.9.0 | 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.