RUSTSEC-2020-0071

See a problem?
Please try reporting it to the source first.
Source
https://rustsec.org/advisories/RUSTSEC-2020-0071
Import Source
https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2020-0071.json
JSON Data
https://api.osv.dev/v1/vulns/RUSTSEC-2020-0071
Aliases
Related
Published
2020-11-18T12:00:00Z
Modified
2024-06-05T14:00:17Z
Severity
  • 6.2 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
Summary
Potential segfault in the time crate
Details

Impact

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's knowledge, notably in the Rust standard library or third-party libraries.

The affected functions from time 0.2.7 through 0.2.22 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
  • time::OffsetDateTime::try_now_local

The affected functions in time 0.1 (all versions) are:

  • time::at_utc
  • time::at
  • time::now
  • time::tzset

Non-Unix targets (including Windows and wasm) are unaffected.

Patches

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.

Users and library authors with time in their dependency tree should perform cargo update, which will pull in the updated, unaffected code.

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.

Workarounds

A possible workaround for crates affected through the transitive dependency in chrono, is to avoid using the default oldtime feature dependency of the chrono crate by disabling its default-features and manually specifying the required features instead.

Examples:

Cargo.toml: 

chrono = { version = "0.4", default-features = false, features = ["serde"] }

chrono = { version = "0.4.22", default-features = false, features = ["clock"] }

Commandline: 

cargo add chrono --no-default-features -F clock

Sources:
- chronotope/chrono#602 (comment)
- vityafx/serde-aux#21

Database specific 
{
    "license": "CC0-1.0"
}
References

Affected packages

crates.io / time

Package

Name
time
View open source insights on deps.dev
Purl
pkg:cargo/time

Affected ranges

Type
SEMVER
Events
Introduced
0.0.0-0
Fixed
0.2.0
Introduced
0.2.1-0
Fixed
0.2.1
Introduced
0.2.2-0
Fixed
0.2.2
Introduced
0.2.3-0
Fixed
0.2.3
Introduced
0.2.4-0
Fixed
0.2.4
Introduced
0.2.5-0
Fixed
0.2.5
Introduced
0.2.6-0
Fixed
0.2.6
Introduced
0.2.7-0
Fixed
0.2.23

Ecosystem specific 

{
    "affected_functions": null,
    "affects": {
        "os": [
            "linux",
            "redox",
            "solaris",
            "android",
            "ios",
            "macos",
            "netbsd",
            "openbsd",
            "freebsd"
        ],
        "functions": [
            "time::OffsetDateTime::now_local",
            "time::OffsetDateTime::try_now_local",
            "time::UtcOffset::current_local_offset",
            "time::UtcOffset::local_offset_at",
            "time::UtcOffset::try_current_local_offset",
            "time::UtcOffset::try_local_offset_at",
            "time::at",
            "time::at_utc",
            "time::now"
        ],
        "arch": []
    }
}

Database specific 

{
    "cvss": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
    "informational": null,
    "categories": [
        "code-execution",
        "memory-corruption"
    ]
}