CVE-2020-26235
low-risk
Published 2020-11-24
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.
Do I need to act?
-
0.64% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
5
CVSS 5.3/10
Medium
NETWORK
/ HIGH complexity
Affected Products (1)
Time
Affected Vendors
References (6)
Release Notes
https://crates.io/crates/time/0.2.23
Issue Tracking
https://github.com/time-rs/time/issues/293
Release Notes
https://crates.io/crates/time/0.2.23
Issue Tracking
https://github.com/time-rs/time/issues/293
24
/ 100
low-risk
Severity
17/34 · Moderate
Exploitability
2/34 · Minimal
Exposure
5/34 · Minimal