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.
References
Link | Resource |
---|---|
https://crates.io/crates/time/0.2.23 | Release Notes Vendor Advisory |
https://github.com/time-rs/time/issues/293 | Issue Tracking Third Party Advisory |
https://github.com/time-rs/time/security/advisories/GHSA-wcg3-cvx6-7396 | Patch Third Party Advisory |
Configurations
Configuration 1 (hide)
AND |
|
History
No history.
Information
Published : 2020-11-24 22:15
Updated : 2020-12-03 19:42
NVD link : CVE-2020-26235
Mitre link : CVE-2020-26235
CVE.ORG link : CVE-2020-26235
JSON object : View
Products Affected
time_project
- time
microsoft
- windows
CWE
CWE-476
NULL Pointer Dereference