Deps.rs

starship 0.36.0

[![dependency status](https://deps.rs/crate/starship/0.36.0/status.svg)](https://deps.rs/crate/starship/0.36.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 starship

Dependencies

(27 total, 17 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 ansi_term^0.12.10.12.1up to date
 battery^0.7.50.7.8up to date
 byte-unit^3.0.35.1.6out of date
 chrono ⚠️^0.40.4.41maybe insecure
 clap^2.33.04.5.40out of date
 dirs^2.0.26.0.0out of date
 gethostname^0.2.11.0.2out of date
 git2^0.11.00.20.2out of date
 log^0.4.80.4.27up to date
 nom^5.1.08.0.0out of date
 once_cell^1.3.11.21.3up to date
 open^1.3.45.3.2out of date
 os_info^2.0.03.12.0out of date
 path-slash^0.1.10.2.1out of date
 pretty_env_logger^0.4.00.5.0out of date
 rayon^1.3.01.10.0up to date
 reqwest^0.10.10.12.22out of date
 serde_json^1.0.471.0.140up to date
 starship_module_config_derive^0.1.00.2.1out of date
 sysinfo^0.11.20.35.2out of date
 term_size^0.3.10.3.2up to date
 textwrap^0.11.00.16.2out of date
 toml^0.5.60.8.23out of date
 unicode-segmentation^1.6.01.12.0up to date
 unicode-width^0.1.70.2.1out of date
 urlencoding^1.0.02.1.3out of date
 yaml-rust ⚠️^0.40.4.5maybe insecure

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 tempfile^3.1.03.20.0up 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