Segmentation fault in Rust time crate
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.2.23, 0.2.0, 0.2.1, 0.2.2, 0.2.3, and 3 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In Rust time crate from version 0.2.7 and before version 0.2.23, 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 and time::OffsetDateTime::try_now_local. Non-Unix targets are unaffected. This includes Windows and wasm. The issue was introduced in version 0.2.7 and fixed in version 0.2.23.
Timeline
- CVE published
- Record last updated
Affected versions
- time-rs time
From 0.2.7 · fixed in 0.2.23
- timecrates.io
From 0.1.0 · fixed in 0.2.23
- timecrates.io
From 0.2.7 · fixed in 0.2.23
- timecrates.io
From 0.0.0-0 · fixed in 0.2.0; From 0.2.1-0 · fixed in 0.2.1; From 0.2.2-0 · fixed in 0.2.2; From 0.2.3-0 · fixed in 0.2.3; From 0.2.4-0 · fixed in 0.2.4; From 0.2.5-0 · fixed in 0.2.5; From 0.2.6-0 · fixed in 0.2.6; From 0.2.7-0 · fixed in 0.2.23