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

Crate instant

Dependencies

(6 total, 2 insecure)

CrateRequiredLatestStatus
 cfg-if^1.01.0.0up to date
 js-sys^0.30.3.50up to date
 stdweb^0.40.4.20insecure
 wasm-bindgen^0.20.2.73up to date
 web-sys^0.30.3.50up to date
 time^0.20.2.26insecure

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 wasm-bindgen-test^0.30.3.23up to date

Security Vulnerabilities

stdweb: stdweb is unmaintained

RUSTSEC-2020-0056

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 the user to set any environment variable in a different thread than the affected functions.

The affected functions 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

Non-Unix targets are unaffected. This includes Windows and wasm.

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 a the updated, unaffected code.

Workarounds

No workarounds are known.

References

#293