This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate chrono


(10 total, 1 outdated, 1 insecure, 1 possibly insecure)

 js-sys^ to date
 libc^0.2.690.2.139up to date
 num-integer^0.1.360.1.45up to date
 num-traits^ to date
 pure-rust-locales^ to date
 rustc-serialize ⚠️^
 serde^1.0.991.0.152up to date
 time ⚠️^0.1.430.3.17out of date
 wasm-bindgen^ to date
 winapi^ to date

Dev dependencies

(7 total, 2 outdated)

 bincode^ of date
 criterion^ of date
 doc-comment^ to date
 num-iter^0.1.350.1.43up to date
 serde_derive^11.0.152up to date
 serde_json^11.0.91up to date
 wasm-bindgen-test^ to date

Security Vulnerabilities

time: Potential segfault in the time crate



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.


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.


No workarounds are known.

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


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.