CVE-2020-26235
Time Project Time vulnerability
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.
Affected products
Time. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Time Project Time runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- crates.io/crates/time/0.2.23 · Vendor Advisory
- github.com/time-rs/time/security/advisories/GHSA-wcg3-cvx6-7396 · Patch
- github.com/time-rs/time/issues/293 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2020-26235
- rustsec.org/advisories/RUSTSEC-2020-0071.html
- github.com/advisories/GHSA-wcg3-cvx6-7396
- nvd.nist.gov/vuln/detail/CVE-2020-26235
- cve.org/CVERecord?id=CVE-2020-26235
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.