Deps.rs

unleash-edge 19.11.0

[![dependency status](https://deps.rs/crate/unleash-edge/19.11.0/status.svg)](https://deps.rs/crate/unleash-edge/19.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 unleash-edge

Dependencies

(57 total, 7 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 actix-allow-deny-middleware^0.1.10.1.2up to date
 actix-cors^0.7.10.7.1up to date
 actix-http^3.11.03.11.2up to date
 actix-middleware-etag^0.4.40.4.6up to date
 actix-service^2.0.32.0.3up to date
 actix-web^4.11.04.12.1up to date
 actix-web-lab^0.24.10.24.3up to date
 ahash^0.8.120.8.12up to date
 anyhow^1.0.981.0.100up to date
 async-trait^0.1.880.1.89up to date
 aws-config^1.6.31.8.12up to date
 aws-sdk-s3^1.90.01.117.0up to date
 base64^0.22.10.22.1up to date
 chrono^0.4.410.4.42up to date
 cidr^0.3.10.3.1up to date
 clap^4.5.394.5.53up to date
 clap-markdown^0.1.50.1.5up to date
 dashmap^6.1.06.1.0up to date
 eventsource-client^0.15.00.15.1up to date
 futures^0.3.310.3.31up to date
 futures-core^0.3.310.3.31up to date
 ipnet^2.11.02.11.0up to date
 itertools^0.14.00.14.0up to date
 json-structural-diff^0.2.00.2.0up to date
 lazy_static^1.5.01.5.0up to date
 num_cpus^1.17.01.17.0up to date
 opentelemetry^0.30.00.31.0out of date
 opentelemetry-prometheus^0.29.10.29.1up to date
 opentelemetry-semantic-conventions^0.30.00.31.0out of date
 opentelemetry_sdk^0.30.00.31.0out of date
 p12-keystore^0.1.50.2.0out of date
 pin-project-lite^0.2.160.2.16up to date
 pkix^0.2.40.2.4up to date
 prometheus^0.14.00.14.0up to date
 prometheus-reqwest-remote-write^0.4.00.4.0up to date
 prometheus-static-metric^0.5.10.5.1up to date
 rand^0.9.10.9.2up to date
 redis^0.31.01.0.1out of date
 reqwest^0.12.190.12.25up to date
 rustls^0.23.270.23.35up to date
 rustls-pemfile^2.2.02.2.0up to date
 rustls-pki-types^1.12.01.13.1up to date
 semver^1.0.261.0.27up to date
 serde^1.0.2191.0.228up to date
 serde_json^1.0.1401.0.145up to date
 serde_qs^0.15.00.15.0up to date
 shadow-rs^1.1.11.4.0up to date
 tokio^1.45.11.48.0up to date
 tokio-stream^0.1.170.1.17up to date
 tracing^0.1.410.1.43up to date
 tracing-subscriber ⚠️^0.3.190.3.22maybe insecure
 ulid^1.2.11.2.1up to date
 unleash-types^0.15.140.15.21up to date
 unleash-yggdrasil^0.17.50.18.1out of date
 utoipa^5.3.15.4.0up to date
 utoipa-swagger-ui^9.0.29.0.2up to date
 zip^3.0.06.0.0out of date

Dev dependencies

(11 total, 2 outdated)

CrateRequiredLatestStatus
 actix-http^3.11.03.11.2up to date
 actix-http-test^3.2.03.2.0up to date
 actix-service^2.0.32.0.3up to date
 capture-logger^0.1.10.1.1up to date
 env_logger^0.11.80.11.8up to date
 maplit^1.0.21.0.2up to date
 rand^0.9.10.9.2up to date
 test-case^3.3.13.3.1up to date
 testcontainers^0.24.00.26.0out of date
 testcontainers-modules^0.12.10.14.0out of date
 tracing-test^0.2.50.2.5up to date

Security Vulnerabilities

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.