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 rouille

Dependencies

(17 total, 9 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 base64^0.9.00.22.0out of date
 brotli2^0.3.20.3.2up to date
 chrono ⚠️^0.4.00.4.37maybe insecure
 deflate^0.71.0.0out of date
 filetime^0.2.00.2.23up to date
 multipart^0.13.60.18.0out of date
 num_cpus^11.16.0up to date
 rand^0.4.20.8.5out of date
 serde^11.0.197up to date
 serde_derive^11.0.197up to date
 serde_json^11.0.115up to date
 sha1^0.6.00.10.6out of date
 term^0.5.10.7.0out of date
 threadpool^11.8.1up to date
 time ⚠️^0.1.310.3.34out of date
 tiny_http ⚠️^0.6.00.12.0out of date
 url^1.22.5.0out of date

Dev dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 log^0.40.4.21up to date
 postgres^0.15.20.19.7out of date

Security Vulnerabilities

tiny_http: HTTP Request smuggling through malformed Transfer Encoding headers

RUSTSEC-2020-0031

HTTP 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 crate

RUSTSEC-2020-0071

Impact

Unix-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_at
  • time::UtcOffset::try_local_offset_at
  • time::UtcOffset::current_local_offset
  • time::UtcOffset::try_current_local_offset
  • time::OffsetDateTime::now_local
  • time::OffsetDateTime::try_now_local

The affected functions in time 0.1 (all versions) are:

  • at
  • at_utc
  • now

Non-Unix targets (including Windows and wasm) are unaffected.

Patches

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.

Workarounds

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.

Examples:

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` invocations

RUSTSEC-2020-0159

Impact

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

Workarounds

No workarounds are known.

References