Segmentation fault in Rust time crate
time-rs time
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| time crates.io |
|
time-rs time
| Product | Affected | Fixed in |
|---|---|---|
| time crates.io |
|
≥ 0.2.6-0 · < 0.2.6≥ 0.2.7-0 · < 0.2.23
|
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.
From the CVE record · GitHub_M
On Unix-like systems, the Rust time crate can segfault when a local time function dereferences a dangling pointer. This can happen if an environment variable is set in another thread while an affected function runs; the input does not specify an attacker access path or required user interaction. Windows and wasm are unaffected.
Check applications using crates.io time versions 0.2.7 through 0.2.22 on Unix-like systems.