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

Crate chrono


(13 total, 3 outdated, 1 insecure, 1 possibly insecure)

 arbitrary^ to date
 criterion^ of date
 iana-time-zone^0.1.450.1.60up to date
 js-sys^ to date
 num-integer^0.1.360.1.46up to date
 num-traits^ to date
 pure-rust-locales^ of date
 rkyv^ to date
 rustc-serialize ⚠️^
 serde^1.0.991.0.203up to date
 time ⚠️^0.1.430.3.36out of date
 wasm-bindgen^ to date
 winapi^ to date

Dev dependencies

(6 total, all up-to-date)

 bincode^ to date
 doc-comment^ to date
 num-iter^0.1.350.1.45up to date
 serde_derive^11.0.203up to date
 serde_json^11.0.117up to date
 wasm-bindgen-test^ to date

Security Vulnerabilities

time: Potential segfault in the time crate



The affected functions set environment variables without synchronization. On Unix-like operating systems, this can crash in multithreaded programs. Programs may segfault due to dereferencing a dangling pointer if an environment variable is read in a different thread than the affected functions. This may occur without the user's knowledge, notably in the Rust standard library or third-party libraries.

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:

  • time::at_utc
  • time::at
  • time::now
  • time::tzset

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.


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.



chrono = { version = "0.4", default-features = false, features = ["serde"] }
chrono = { version = "0.4.22", default-features = false, features = ["clock"] }


cargo add chrono --no-default-features -F clock


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.