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 binance-sdk

Dependencies

(31 total, 7 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.102up to date
 serde_json^1.01.0.149up to date
 serde_repr^0.10.1.20up to date
 url^2.52.5.8up to date
 async-trait^0.10.1.89up to date
 thiserror^2.0.122.0.18up to date
 regex^1.101.12.3up to date
 hmac^0.120.13.0out of date
 sha2^0.100.11.0out of date
 hex^0.40.4.3up to date
 base64^0.220.22.1up to date
 flate2^1.01.1.9up to date
 derive_builder^0.100.20.2out of date
 tokio-stream^0.10.1.18up to date
 rand^0.80.10.1out of date
 futures^0.30.3.32up to date
 http^11.4.0up to date
 tracing^0.10.1.44up to date
 once_cell^1.211.21.4up to date
 openssl ⚠️^0.100.10.78maybe insecure
 tokio-native-tls^0.30.3.1up to date
 serde^1.01.0.228up to date
 uuid^1.81.23.1up to date
 reqwest^0.120.13.2out of date
 reqwest-middleware^0.30.5.1out of date
 tokio^1.331.52.1up to date
 ed25519-dalek^2.12.2.0up to date
 tokio-tungstenite^0.260.29.0out of date
 tokio-util^0.70.7.18up to date
 tracing-subscriber ⚠️^0.30.3.23maybe insecure
 rust_decimal^1.37.21.41.0up to date

Dev dependencies

(5 total, 1 outdated)

CrateRequiredLatestStatus
 httpmock^0.60.8.3out of date
 mockito^1.2.01.7.2up to date
 tempfile^3.20.03.27.0up to date
 futures-util^0.30.3.32up to date
 tokio-test^0.40.4.5up to date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 rustc_version^0.40.4.1up to date

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.