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 projvar

Dependencies

(24 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 askalono^0.50.5.0up to date
 chrono ⚠️^0.40.4.45maybe insecure
 clap^4.64.6.3up to date
 cli_utils_hoijui^0.130.13.0up to date
 const_format^0.20.2.36up to date
 enum-map^2.73.1.0out of date
 git-version^0.30.3.9up to date
 git2^0.210.21.0up to date
 gix-url^0.360.36.2up to date
 human-panic^2.02.0.8up to date
 log^0.40.4.33up to date
 proc-macro2^1.01.0.107up to date
 regex^1.131.13.1up to date
 remain^0.20.2.16up to date
 repvar^0.140.14.4up to date
 serde^1.01.0.229up to date
 serde_json^1.01.0.151up to date
 spdx^0.130.13.4up to date
 strum^0.280.28.0up to date
 strum_macros^0.280.28.0up to date
 thiserror^2.02.0.19up to date
 tracing^0.10.1.44up to date
 tracing-subscriber ⚠️^0.30.3.23maybe insecure
 url^2.52.5.8up to date

Dev dependencies

(8 total, all up-to-date)

CrateRequiredLatestStatus
 assert_cmd^2.22.2.2up to date
 assert_fs^1.11.1.4up to date
 cmd_lib^2.02.0.0up to date
 const-fnv1a-hash^1.11.1.0up to date
 directories^6.06.0.0up to date
 fake^5.15.1.0up to date
 predicates^3.13.1.4up to date
 uuid^1.231.24.0up to date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 reqwest^0.130.13.4up to date

Security Vulnerabilities

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

tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequences

RUSTSEC-2025-0055

Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:

  • Manipulate terminal title bars
  • Clear screens or modify terminal display
  • Potentially mislead users through terminal manipulation

In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.

This was patched in PR #3368 to escape ANSI control characters from user input.