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 rabbitmq-stream-client

Dependencies

(16 total, 1 outdated)

CrateRequiredLatestStatus
 tokio-rustls^0.26.10.26.4up to date
 rustls-pemfile^2.2.02.2.0up to date
 tokio^1.29.11.48.0up to date
 tokio-util^0.7.30.7.17up to date
 bytes^1.0.01.11.0up to date
 pin-project^1.0.01.1.10up to date
 tokio-stream^0.1.110.1.17up to date
 futures^0.3.00.3.31up to date
 url^2.2.22.5.7up to date
 tracing^0.10.1.41up to date
 thiserror^2.02.0.17up to date
 async-trait^0.1.510.1.89up to date
 rand^0.80.9.2out of date
 dashmap^6.1.06.1.0up to date
 murmur3^0.5.20.5.2up to date
 serde^1.01.0.228up to date

Dev dependencies

(6 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tracing-subscriber ⚠️^0.3.10.3.20maybe insecure
 fake^4.2.04.4.0up to date
 chrono^0.4.260.4.42up to date
 serde_json^1.01.0.145up to date
 reqwest^0.120.12.24up to date
 serde^1.01.0.228up to date

Crate rabbitmq-stream-protocol

Dependencies

(6 total, 1 outdated)

CrateRequiredLatestStatus
 byteorder^11.5.0up to date
 ordered-float^4.1.05.1.0out of date
 uuid^11.18.1up to date
 chrono^0.4.260.4.42up to date
 num_enum^0.7.00.7.5up to date
 derive_more^2.0.12.0.1up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 pretty_assertions^1.2.01.4.1up to date
 fake^4.04.4.0up to date

Crate benchmark

Dependencies

(6 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tracing-subscriber ⚠️^0.3.10.3.20maybe insecure
 tracing^0.10.1.41up to date
 tokio^1.29.11.48.0up to date
 clap^4.0.224.5.52up to date
 futures^0.3.00.3.31up to date
 async-trait^0.1.510.1.89up 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.