Deps.rs

~alip / syd

[![dependency status](https://deps.rs/repo/sourcehut/~alip/syd/status.svg)](https://deps.rs/repo/sourcehut/~alip/syd)

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 syd

Dependencies

(55 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 ahash^0.80.8.12up to date
 bitflags^2.112.11.1up to date
 btoi^0.50.5.0up to date
 cfg-if^1.01.0.4up to date
 data-encoding^2.102.11.0up to date
 dur^0.50.5.3up to date
 expiringmap^0.10.1.2up to date
 fixedbitset^0.50.5.7up to date
 indexmap^2.132.14.0up to date
 ipnet^2.122.12.0up to date
 iprange^0.60.6.7up to date
 itoa^1.01.0.18up to date
 lexopt^0.30.3.2up to date
 libc^0.20.2.186up to date
 libloading^0.80.9.0out of date
 libseccomp^0.40.4.0up to date
 libseccomp-sys^0.30.3.0up to date
 memchr^2.82.8.0up to date
 netlink-sys^0.80.8.8up to date
 nix^0.310.31.2up to date
 nom^8.08.0.0up to date
 num_cpus^1.171.17.0up to date
 parse-size^1.11.1.0up to date
 redix^1.2.31.4.1up to date
 procfs^0.180.18.0up to date
 procfs-core^0.180.18.0up to date
 retry^2.22.2.0up to date
 ringbuf^0.40.4.8up to date
 shellexpand^3.13.1.2up to date
 shell-words^1.11.1.1up to date
 serde_core^1.01.0.228up to date
 serde_json^1.01.0.149up to date
 sha3^0.100.11.0out of date
 io-uring=0.60.7.12out of date
 subtle^2.62.6.1up to date
 lexis^0.20.2.5up to date
 zeroize^1.81.8.2up to date
 iced-x86^1.211.21.0up to date
 raki^1.31.3.2up to date
 yaxpeax-arch^0.30.3.2up to date
 yaxpeax-arm^0.40.4.0up to date
 rpassword^7.47.5.1up to date
 linefeed^0.6.00.6.0up to date
 gperftools^0.20.2.0up to date
 tcmalloc^0.30.3.0up to date
 clap^4.54.6.1up to date
 libcgroups^0.60.6.0up to date
 libcontainer^0.60.6.0up to date
 liboci-cli^0.60.6.0up to date
 oci-spec^0.90.9.0up to date
 tabwriter^1.41.4.1up to date
 tracing^0.10.1.44up to date
 tracing-subscriber ⚠️^0.30.3.23maybe insecure
 hardened-malloc^13.0.116.0.2026040801out of date
 tick_counter^0.40.4.5up to date

Dev dependencies

(6 total, 1 outdated)

CrateRequiredLatestStatus
 brunch^0.80.11.1out of date
 goblin^0.100.10.5up to date
 strum^0.280.28.0up to date
 strum_macros^0.280.28.0up to date
 tempfile^3.273.27.0up to date
 xz2^0.10.1.7up to date

Build dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 cc^1.21.2.61up to date
 libc^0.20.2.186up to date
 pkg-config^0.30.3.33up to date

Crate hardened-malloc

Dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 hardened-malloc-sys^13.0.016.0.2026040801out of date

Crate hardened-malloc-sys

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 cc^1.01.2.61up to date

Crate libsyd

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 pkg-config^0.30.3.33up to date

Crate pandora_box

Dependencies

(19 total, all up-to-date)

CrateRequiredLatestStatus
 ahash^0.80.8.12up to date
 btoi^0.50.5.0up to date
 console^0.16.00.16.3up to date
 fixedbitset^0.50.5.7up to date
 data-encoding^2.102.11.0up to date
 indicatif^0.18.00.18.4up to date
 lexopt^0.30.3.2up to date
 libc^0.20.2.186up to date
 memchr^2.82.8.0up to date
 nix^0.310.31.2up to date
 num_cpus^1.171.17.0up to date
 rayon^1.10.01.12.0up to date
 serde_core^1.01.0.228up to date
 serde_json^1.01.0.149up to date
 tempfile^3.273.27.0up to date
 patricia_tree^0.100.10.1up to date
 dns-lookup^3.03.0.1up to date
 resolv-conf^0.70.7.6up to date
 simple-dns^0.110.11.2up to date

Dev dependencies

(1 total, 1 possibly insecure)

CrateRequiredLatestStatus
 regex ⚠️^11.12.3maybe insecure

Crate redix

Dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 libc^0.20.2.186up to date
 nix^0.31.20.31.2up to date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 cc^1.21.2.61up to date

Crate syd-tui

Dependencies

(6 total, 1 outdated)

CrateRequiredLatestStatus
 data-encoding^2.102.11.0up to date
 libc^0.20.2.186up to date
 nix^0.310.31.2up to date
 ratatui^0.290.30.0out of date
 termion^4.04.0.6up to date
 tokio^1.501.52.1up 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.