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 cloud-identity-wallet

Dependencies

(13 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 async-stream^0.30.3.6up to date
 aws-config^11.12.0up to date
 axum^0.80.8.9up to date
 config^0.150.15.25up to date
 parking_lot^0.120.12.5up to date
 secrecy^0.100.10.3up to date
 serde_qs^1.11.1.3up to date
 tokio ⚠️^11.53.1maybe insecure
 tower-http^0.60.7.1out of date
 tracing-subscriber ⚠️^0.30.3.23maybe insecure
 x509-parser^0.180.18.1up to date
 redis^1.21.7.0up to date
 tikv-jemallocator^0.60.7.0out of date

Dev dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 reqwest^0.130.13.4up to date
 tempfile^33.27.0up to date
 testcontainers-modules^0.150.15.0up to date
 tower^0.50.5.3up to date

Crate cloud-wallet-crypto

Dependencies

(5 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 aws-lc-rs^1.151.18.1up to date
 num-bigint^0.40.5.1out of date
 pkcs8^0.110.11.0up to date
 serde_with^33.22.0up to date
 simple_asn1 ⚠️^0.60.6.4maybe insecure

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 hex-literal^11.1.0up to date

Crate cloud-wallet-kms

Dependencies

(4 total, all up-to-date)

CrateRequiredLatestStatus
 aws-sdk-kms^11.118.0up to date
 ahash^0.80.8.12up to date
 moka^0.120.12.16up to date
 aws-config^11.12.0up to date

Dev dependencies

(3 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 pollster^0.41.0.1out of date
 tracing-subscriber ⚠️^0.30.3.23maybe insecure
 testcontainers-modules^0.150.15.0up to date

Crate cloud-wallet-openid4vc

Dependencies

(10 total, 1 outdated)

CrateRequiredLatestStatus
 csscolorparser^0.80.8.4up to date
 futures^0.30.3.34up to date
 percent-encoding^22.3.2up to date
 reqwest^0.130.13.4up to date
 reqwest-middleware^0.50.5.2up to date
 reqwest-retry^0.90.9.1up to date
 serde_urlencoded^0.70.7.1up to date
 validator^0.200.21.0out of date
 webpki-roots^11.0.9up to date
 x509-parser^0.180.18.1up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 wiremock^0.60.6.5up to date

Crate xtask

Dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 clap^44.6.6up to date

Security Vulnerabilities

simple_asn1: Panic on incorrect date input to `simple_asn1`

RUSTSEC-2021-0125

Version 0.6.0 of the simple_asn1 crate panics on certain malformed inputs to its parsing functions, including from_der and der_decode. Because this crate is frequently used with inputs from the network, this should be considered a security vulnerability.

The issue occurs when parsing the old ASN.1 "UTCTime" time format. If an attacker provides a UTCTime where the first character is ASCII but the second character is above 0x7f, a string slice operation in the from_der_ function will try to slice into the middle of a UTF-8 character, and cause a panic.

This error was introduced in commit d7d39d709577710e9dc8, which updated simple_asn1 to use time instead of chrono because of RUSTSEC-2020-159. Versions of simple_asn1 before 0.6.0 are not affected by this issue.

The patch was applied in simple_asn1 version 0.6.1.

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.