This project contains known security vulnerabilities. Find detailed information at the bottom.
rouille(12 total, 11 outdated, 1 insecure, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| brotli2 | ^0.2.1 | 0.3.2 | out of date |
| chrono ⚠️ | ^0.2.0 | 0.4.38 | out of date |
| filetime | ^0.1.10 | 0.2.23 | out of date |
| flate2 | ^0.2.14 | 1.0.30 | out of date |
| multipart | ^0.5.1 | 0.18.0 | out of date |
| rand | ^0.3.11 | 0.8.5 | out of date |
| rustc-serialize ⚠️ | ^0.3 | 0.3.25 | insecure |
| sha1 | ^0.2.0 | 0.10.6 | out of date |
| term | ^0.2 | 0.7.0 | out of date |
| time ⚠️ | ^0.1.31 | 0.3.36 | out of date |
| tiny_http ⚠️ | ^0.5.6 | 0.12.0 | out of date |
| url | ^1.2 | 2.5.0 | out of date |
(1 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| postgres | ^0.13 | 0.19.7 | out of date |
tiny_http: HTTP Request smuggling through malformed Transfer Encoding headersHTTP pipelining issues and request smuggling attacks are possible due to incorrect Transfer encoding header parsing.
It is possible conduct HTTP request smuggling attacks (CL:TE/TE:TE) by sending invalid Transfer Encoding headers.
By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack, or obtain sensitive information from requests other than their own.
time: Potential segfault in the time crateUnix-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.
The affected functions from time 0.2.7 through 0.2.22 are:
time::UtcOffset::local_offset_attime::UtcOffset::try_local_offset_attime::UtcOffset::current_local_offsettime::UtcOffset::try_current_local_offsettime::OffsetDateTime::now_localtime::OffsetDateTime::try_now_localThe affected functions in time 0.1 (all versions) are:
atat_utcnowNon-Unix targets (including Windows and wasm) are unaffected.
Pending a proper fix, the internal method that determines the local offset has been modified to always return None on the affected operating systems. This has the effect of returning an Err on the try_* methods and UTC on the non-try_* methods.
Users and library authors with time in their dependency tree should perform cargo update, which will pull in the updated, unaffected code.
Users of time 0.1 do not have a patch and should upgrade to an unaffected version: time 0.2.23 or greater or the 0.3 series.
A possible workaround for crates affected through the transitive dependency in chrono, is to avoid using the default oldtime feature dependency of the chrono crate by disabling its default-features and manually specifying the required features instead.
Cargo.toml:
chrono = { version = "0.4", default-features = false, features = ["serde"] }
chrono = { version = "0.4.22", default-features = false, features = ["clock"] }
Commandline:
cargo add chrono --no-default-features -F clock
Sources:
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.