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 azure_identity

Dependencies

(12 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-lock^3.03.4.2up to date
 async-trait^0.10.1.89up to date
 azure_core^0.31.00.32.0out of date
 futures^0.30.3.32up to date
 openssl^0.10.720.10.75up to date
 pin-project^1.01.1.10up to date
 serde^1.01.0.228up to date
 serde_json^1.01.0.149up to date
 time ⚠️^0.3.410.3.47maybe insecure
 tokio ⚠️^1.01.49.0maybe insecure
 tracing^0.1.400.1.44up to date
 url^2.22.5.8up to date

Dev dependencies

(8 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 clap^4.5.454.5.60up to date
 include-file^0.5.10.5.1up to date
 reqwest^0.12.230.13.2out of date
 serde_json^1.01.0.149up to date
 serde_test^11.0.177up to date
 serial_test^3.03.4.0up to date
 tokio ⚠️^1.01.49.0maybe insecure
 tracing-subscriber ⚠️^0.30.3.22maybe insecure

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.

time: Denial of Service via Stack Exhaustion

RUSTSEC-2026-0009

Impact

When user-provided input is provided to any type that parses with the RFC 2822 format, a denial of service attack via stack exhaustion is possible. The attack relies on formally deprecated and rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary, non-malicious input will never encounter this scenario.

Patches

A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned rather than exhausting the stack.

Workarounds

Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of the stack consumed would be at most a factor of the length of the input.