Deps.rs

cargo-crev 0.16.1

[![dependency status](https://deps.rs/crate/cargo-crev/0.16.1/status.svg)](https://deps.rs/crate/cargo-crev/0.16.1)

This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate cargo-crev

Dependencies

(29 total, 18 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 atty^0.20.2.14up to date
 cargo^0.420.78.1out of date
 cargo-platform^0.10.1.8up to date
 common_failures^0.10.2.0out of date
 crates_io_api^0.50.11.0out of date
 crev-common^0.16.00.25.4out of date
 crev-data^0.16.00.25.7out of date
 crev-lib^0.16.00.25.4out of date
 crossbeam^0.70.8.4out of date
 crossterm^0.9.60.27.0out of date
 env_logger^0.6.20.11.3out of date
 failure^0.10.1.8up to date
 geiger^0.3.20.4.12out of date
 insideout^0.20.2.0up to date
 lazy_static^1.31.4.0up to date
 num_cpus^1.101.16.0up to date
 petgraph^0.4.130.6.4out of date
 rayon^1.11.10.0up to date
 resiter^0.30.5.0out of date
 semver^0.91.0.22out of date
 serde^11.0.198up to date
 serde_json^11.0.116up to date
 serde_yaml^0.8.110.9.34+deprecatedout of date
 structopt^0.30.3.26up to date
 term^0.60.7.0out of date
 termimad^0.60.29.1out of date
 time ⚠️^0.1.420.3.36out of date
 tokei^1012.1.2out of date
 walkdir^22.5.0up to date

Security Vulnerabilities

time: Potential segfault in the time crate

RUSTSEC-2020-0071

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

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:

  • at
  • at_utc
  • now

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: