https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 00:19:09 +0000 https://cve.radiocsirt.org/vuln/cve-2020-26235 <p><strong>Affected:</strong> time-rs time</p> <p>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.</p> <p><strong>Affected:</strong> time-rs time</p> <p>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.</p> https://cve.radiocsirt.org/vuln/cve-2020-26235 https://cve.radiocsirt.org/vuln/rustsec-2020-0071 <p><strong>Affected:</strong> crates.io: time</p> <p>### Impact</p> <p>The affected functions set environment variables without synchronization. On Unix-like operating systems, this can crash in multithreaded programs. Programs may segfault due to dereferencing a dangling pointer if an environment variable is read in a different thread than the affected functions. This may occur without the user&#39;s knowledge, notably in the Rust standard library or third-party libraries.</p> <p>The affected functions from time 0.2.7 through 0.2.22 are:</p> <p>- `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` - `time::OffsetDateTime::try_now_local`</p> <p>The affected functions in time 0.1 (all versions) are:</p> <p>- `time::at_utc` - `time::at` - `time::now` - `time::tzset`</p> <p>Non-Unix targets (including Windows and wasm) are unaffected.</p> <p>### Patches</p> <p>Pending a proper fix, the internal method that determines the local offset has been modified to always return `None` on the affected operating systems. This has the effect of returning an `Err` on the `try_*` methods and `UTC` on the non-`try_*` methods.</p> <p>Users and library authors with time in their dependency tree should perform `cargo update`, which will pull in the updated, unaffected code.</p> <p>Users of time 0.1 do not have a patch and should upgrade to an unaffected version: time 0.2.23 or greater or the 0.3 series.</p> <p>### Workarounds</p> <p>A possible workaround for crates affected thr…</p> <p><strong>Affected:</strong> crates.io: time</p> <p>### Impact</p> <p>The affected functions set environment variables without synchronization. On Unix-like operating systems, this can crash in multithreaded programs. Programs may segfault due to dereferencing a dangling pointer if an environment variable is read in a different thread than the affected functions. This may occur without the user&#39;s knowledge, notably in the Rust standard library or third-party libraries.</p> <p>The affected functions from time 0.2.7 through 0.2.22 are:</p> <p>- `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` - `time::OffsetDateTime::try_now_local`</p> <p>The affected functions in time 0.1 (all versions) are:</p> <p>- `time::at_utc` - `time::at` - `time::now` - `time::tzset`</p> <p>Non-Unix targets (including Windows and wasm) are unaffected.</p> <p>### Patches</p> <p>Pending a proper fix, the internal method that determines the local offset has been modified to always return `None` on the affected operating systems. This has the effect of returning an `Err` on the `try_*` methods and `UTC` on the non-`try_*` methods.</p> <p>Users and library authors with time in their dependency tree should perform `cargo update`, which will pull in the updated, unaffected code.</p> <p>Users of time 0.1 do not have a patch and should upgrade to an unaffected version: time 0.2.23 or greater or the 0.3 series.</p> <p>### Workarounds</p> <p>A possible workaround for crates affected thr…</p> https://cve.radiocsirt.org/vuln/rustsec-2020-0071