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.

Crate tiny_http

Dependencies

(8 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 ascii^1.01.1.0up to date
 chunked_transfer^11.5.0up to date
 httpdate^1.0.21.0.3up to date
 log^0.4.40.4.22up to date
 openssl ⚠️^0.100.10.65maybe insecure
 rustls ⚠️^0.200.23.11out of date
 rustls-pemfile^0.2.12.1.2out of date
 zeroize^11.8.1up to date

Dev dependencies

(3 total, 2 outdated, 1 insecure)

CrateRequiredLatestStatus
 fdlimit^0.10.3.0out of date
 rustc-serialize ⚠️^0.30.3.25insecure
 sha1^0.6.00.10.6out of date

Security Vulnerabilities

rustc-serialize: Stack overflow in rustc_serialize when parsing deeply nested JSON

RUSTSEC-2022-0004

When 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: `openssl` `X509VerifyParamRef::set_host` buffer over-read

RUSTSEC-2023-0044

When this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.

rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input

RUSTSEC-2024-0336

If 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.