Deps.rs

AndPuQing / gflow

[![dependency status](https://deps.rs/repo/github/AndPuQing/gflow/status.svg)](https://deps.rs/repo/github/AndPuQing/gflow)

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 gflow

Dependencies

(28 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 tmux_interface^0.3.20.3.2up to date
 tokio^1.43.01.49.0up to date
 clap^4.5.284.5.54up to date
 clap_complete^4.5.444.5.65up to date
 tracing^0.1.400.1.44up to date
 tracing-subscriber ⚠️^0.3.180.3.22maybe insecure
 prometheus^0.13.40.14.0out of date
 lazy_static^1.4.01.5.0up to date
 reqwest^0.13.00.13.1up to date
 axum^0.8.00.8.8up to date
 config^0.15.70.15.19up to date
 dirs^6.0.06.0.0up to date
 serde^1.0.2171.0.228up to date
 anyhow^1.0.951.0.100up to date
 strum^0.27.00.27.2up to date
 nvml-wrapper^0.11.00.11.0up to date
 serde_json^1.01.0.149up to date
 rusqlite^0.380.38.0up to date
 uuid^1.10.01.19.0up to date
 range-parser^0.1.20.1.2up to date
 tabled^0.20.00.20.0up to date
 owo-colors^4.1.04.2.3up to date
 shell-escape^0.1.50.1.5up to date
 regex ⚠️^11.12.2maybe insecure
 csv^1.31.4.0up to date
 socket2^0.60.6.1up to date
 libc^0.20.2.180up to date
 clap-verbosity-flag^3.0.43.0.4up to date

Dev dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 mockall^0.14.00.14.0up to date
 tempfile^3.16.03.24.0up to date
 nvml-wrapper^0.11.00.11.0up to date
 tower^0.50.5.2up to date

Build dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 anyhow^1.0.951.0.100up to date
 vergen-gix^1.0.61.0.9up to date

Security Vulnerabilities

regex: Regexes with large repetitions on empty sub-expressions take a very long time to parse

RUSTSEC-2022-0013

The Rust Security Response WG was notified that the regex crate did not properly limit the complexity of the regular expressions (regex) it parses. An attacker could use this security issue to perform a denial of service, by sending a specially crafted regex to a service accepting untrusted regexes. No known vulnerability is present when parsing untrusted input with trusted regexes.

This issue has been assigned CVE-2022-24713. The severity of this vulnerability is "high" when the regex crate is used to parse untrusted regexes. Other uses of the regex crate are not affected by this vulnerability.

Overview

The regex crate features built-in mitigations to prevent denial of service attacks caused by untrusted regexes, or untrusted input matched by trusted regexes. Those (tunable) mitigations already provide sane defaults to prevent attacks. This guarantee is documented and it's considered part of the crate's API.

Unfortunately a bug was discovered in the mitigations designed to prevent untrusted regexes to take an arbitrary amount of time during parsing, and it's possible to craft regexes that bypass such mitigations. This makes it possible to perform denial of service attacks by sending specially crafted regexes to services accepting user-controlled, untrusted regexes.

Affected versions

All versions of the regex crate before or equal to 1.5.4 are affected by this issue. The fix is include starting from regex 1.5.5.

Mitigations

We recommend everyone accepting user-controlled regexes to upgrade immediately to the latest version of the regex crate.

Unfortunately there is no fixed set of problematic regexes, as there are practically infinite regexes that could be crafted to exploit this vulnerability. Because of this, we do not recommend denying known problematic regexes.

Acknowledgements

We want to thank Addison Crump for responsibly disclosing this to us according to the Rust security policy, and for helping review the fix.

We also want to thank Andrew Gallant for developing the fix, and Pietro Albini for coordinating the disclosure and writing this advisory.

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.