Deps.rs

config 0.11.0

[![dependency status](https://deps.rs/crate/config/0.11.0/status.svg)](https://deps.rs/crate/config/0.11.0)

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 config

Dependencies

(8 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 lazy_static^1.01.5.0up to date
 nom^5.0.07.1.3out of date
 rust-ini^0.130.21.1out of date
 serde^1.0.81.0.214up to date
 serde-hjson^0.91.1.0out of date
 serde_json^1.0.21.0.132up to date
 toml^0.50.8.19out of date
 yaml-rust ⚠️^0.40.4.5maybe insecure

Dev dependencies

(3 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 chrono ⚠️^0.40.4.38maybe insecure
 float-cmp^0.60.10.0out of date
 serde_derive^1.0.81.0.214up to date

Security Vulnerabilities

yaml-rust: Uncontrolled recursion leads to abort in deserialization

RUSTSEC-2018-0006

Affected versions of this crate did not prevent deep recursion while deserializing data structures.

This allows an attacker to make a YAML file with deeply nested structures that causes an abort while deserializing it.

The flaw was corrected by checking the recursion depth.

Note: clap 2.33 is not affected by this because it uses yaml-rust in a way that doesn't trigger the vulnerability. More specifically:

  1. The input to the YAML parser is always trusted - is included at compile time via include_str!.

  2. The nesting level is never deep enough to trigger the overflow in practice (at most 5).

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

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.

Workarounds

No workarounds are known.

References