RUSTSEC-2020-0071

Potential segfault in the time crate

Issued
Package
time (crates.io)
Type
Vulnerability
Categories
  • code-execution
  • memory-corruption
Aliases
Details
https://github.com/time-rs/time/issues/293
CVSS
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Patched
  • >=0.2.23
Unaffected
  • <0.2.7
Keywords
  • segfault
Affected OSes
  • linux
  • unknown
  • unknown
  • android
  • ios
  • macos
  • netbsd
  • openbsd
  • bitrig
  • freebsd
Affected Functions
Version
time::OffsetDateTime::now_local
  • <0.2.23
time::OffsetDateTime::try_now_local
  • <0.2.23
time::UtcOffset::current_local_offset
  • <0.2.23
time::UtcOffset::local_offset_at
  • <0.2.23
time::UtcOffset::try_current_local_offset
  • <0.2.23
time::UtcOffset::try_local_offset_at
  • <0.2.23

Description

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:

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

More