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 tic

Dependencies

(13 total, 8 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 allan^0.2.20.2.4up to date
 clocksource^0.4.00.8.1out of date
 fnv^1.0.51.0.7up to date
 getopts^0.2.140.2.21up to date
 heatmap^0.6.50.7.8out of date
 histogram^0.6.60.9.1out of date
 log^0.3.80.4.21out of date
 mio^0.6.90.8.11out of date
 mio-extras^2.0.52.0.6up to date
 mpmc^0.1.20.1.6up to date
 time ⚠️^0.1.370.3.34out of date
 tiny_http ⚠️^0.5.80.12.0out of date
 waterfall^0.7.00.8.1out of date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 rand^0.3.160.8.5out 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: