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(6 total, 3 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| ascii | ^0.8 | 1.1.0 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.38 | maybe insecure |
| chunked_transfer | ^0.3 | 1.5.0 | out of date |
| log | ^0.4 | 0.4.22 | up to date |
| openssl ⚠️ | ^0.10 | 0.10.68 | maybe insecure |
| url | ^1.7 | 2.5.3 | out of date |
(2 total, 1 outdated, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| rustc-serialize ⚠️ | ^0.3 | 0.3.25 | insecure |
| sha1 | ^0.6.0 | 0.10.6 | out of date |
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.
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.
openssl: `MemBio::get_buf` has undefined behavior with empty buffersPreviously, MemBio::get_buf called slice::from_raw_parts with a null-pointer, which violates the functions invariants, leading to undefined behavior. In debug builds this would produce an assertion failure. This is now fixed.