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 oo7

Dependencies

(31 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 aes^0.80.8.4up to date
 ashpd^0.130.13.3up to date
 async-fs^2.2.02.2.0up to date
 async-io^2.6.02.6.0up to date
 async-lock^3.4.23.4.2up to date
 blocking^1.5.11.6.2up to date
 cbc^0.10.1.2up to date
 cipher^0.40.5.1out of date
 digest^0.100.11.1out of date
 endi^1.11.1.1up to date
 futures-lite^2.62.6.1up to date
 futures-util^0.30.3.32up to date
 getrandom^0.40.4.1up to date
 hkdf^0.120.12.4up to date
 hmac^0.120.12.1up to date
 md-5^0.100.10.6up to date
 num^0.4.00.4.3up to date
 num-bigint-dig^0.90.9.1up to date
 oo7-macros^0.60.6.0up to date
 openssl ⚠️^0.100.10.75maybe insecure
 pbkdf2^0.120.12.2up to date
 serde^1.01.0.228up to date
 serde_bytes^0.110.11.19up to date
 sha2^0.100.10.9up to date
 subtle^2.52.6.1up to date
 tokio^1.481.50.0up to date
 tracing^0.10.1.44up to date
 zbus^5.12.05.14.0up to date
 zbus_macros^5.115.14.0up to date
 zeroize^11.8.2up to date
 zvariant^5.85.10.0up to date

Dev dependencies

(4 total, 1 possibly insecure)

CrateRequiredLatestStatus
 serial_test^3.33.4.0up to date
 tempfile^3.253.26.0up to date
 tokio^1.481.50.0up to date
 tracing-subscriber ⚠️^0.30.3.22maybe insecure

Security Vulnerabilities

openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`

RUSTSEC-2025-0022

When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.

In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).

The maintainers thank quitbug for reporting this vulnerability to us.

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.