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 duo

Dependencies

(14 total, 7 outdated)

CrateRequiredLatestStatus
 datafusion^4251.0.0out of date
 arrow-schema^53.057.1.0out of date
 axum^0.70.8.7out of date
 clap^44.5.53up to date
 parking_lot^0.120.12.5up to date
 time^0.30.3.44up to date
 tokio^1.391.48.0up to date
 tower^0.40.5.2out of date
 rust-embed^8.58.9.0up to date
 mime_guess^22.0.5up to date
 object_store^0.110.12.4out of date
 url^2.5.22.5.7up to date
 toml^0.8.190.9.8out of date
 tower-http^0.5.20.6.7out of date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 rstest^0.220.26.1out of date

Crate duo-api

Dependencies

(2 total, 2 outdated)

CrateRequiredLatestStatus
 prost^0.130.14.1out of date
 prost-types^0.130.14.1out of date

Crate duo-subscriber

Dependencies

(1 total, 1 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^11.48.0maybe insecure

Dev dependencies

(3 total, 2 possibly insecure)

CrateRequiredLatestStatus
 tokio ⚠️^11.48.0maybe insecure
 tracing-subscriber ⚠️^0.30.3.22maybe insecure
 log^0.40.4.28up to date

Security Vulnerabilities

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);

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.