Deps.rs

opendal 0.55.0

[![dependency status](https://deps.rs/crate/opendal/0.55.0/status.svg)](https://deps.rs/crate/opendal/0.55.0)

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 opendal

Dependencies

(72 total, 8 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.1001.0.100up to date
 async-backtrace^0.2.60.2.7up to date
 await-tree^0.30.3.1up to date
 backon^1.61.6.0up to date
 base64^0.220.22.1up to date
 bb8^0.90.9.0up to date
 bytes^1.61.11.0up to date
 cacache^13.013.1.0up to date
 compio^0.16.00.16.1up to date
 crc32c^0.6.60.6.8up to date
 dashmap^66.1.0up to date
 dotenvy^0.150.15.7up to date
 etcd-client^0.170.17.0up to date
 fastmetrics^0.4.10.4.1up to date
 fastrace^0.7.140.7.14up to date
 flume^0.110.11.1up to date
 foundationdb^0.9.00.10.0out of date
 futures^0.30.3.31up to date
 futures-rustls^0.26.00.26.0up to date
 getrandom^0.20.3.4out of date
 ghac^0.2.00.2.0up to date
 governor^0.10.10.10.2up to date
 hdfs-native^0.130.13.0up to date
 hdrs^0.3.20.3.2up to date
 hmac^0.12.10.12.1up to date
 http^1.11.3.1up to date
 http-body^11.0.1up to date
 jiff^0.2.150.2.16up to date
 js-sys^0.3.770.3.82up to date
 log^0.40.4.28up to date
 md-5^0.100.10.6up to date
 metrics^0.240.24.2up to date
 mime_guess^2.0.52.0.5up to date
 mini-moka^0.100.10.3up to date
 moka^0.120.12.11up to date
 mongodb^3.3.03.4.1up to date
 mongodb-internal-macros^3.2.43.4.1up to date
 monoio^0.2.40.2.4up to date
 openssh^0.11.00.11.5up to date
 openssh-sftp-client^0.15.30.15.4up to date
 opentelemetry^0.31.00.31.0up to date
 ouroboros^0.18.40.18.5up to date
 percent-encoding^22.3.2up to date
 persy^1.7.11.7.1up to date
 probe^0.5.10.5.2up to date
 prometheus^0.140.14.0up to date
 prometheus-client^0.240.24.0up to date
 prost^0.130.14.1out of date
 quick-xml^0.380.38.4up to date
 rand^0.80.9.2out of date
 redb^23.1.0out of date
 redis^0.320.32.7up to date
 reqsign^0.16.50.18.1out of date
 reqwest^0.12.240.12.24up to date
 rocksdb^0.21.00.24.0out of date
 rustls-native-certs^0.80.8.2up to date
 serde^11.0.228up to date
 serde_json^11.0.145up to date
 sha1^0.10.60.10.6up to date
 sha2^0.100.10.9up to date
 sled^0.34.70.34.7up to date
 sqlx ⚠️^0.8.00.8.6maybe insecure
 suppaftp^6.3.07.0.7out of date
 surrealdb^22.3.10up to date
 tikv-client^0.3.00.3.0up to date
 tokio^1.481.48.0up to date
 tracing^0.10.1.41up to date
 url^2.52.5.7up to date
 uuid^1.181.18.1up to date
 wasm-bindgen^0.2.1000.2.105up to date
 wasm-bindgen-futures^0.4.500.4.55up to date
 web-sys^0.3.770.3.82up to date

Dev dependencies

(16 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 criterion^0.70.7.0up to date
 divan^0.10.1.21up to date
 dotenvy^0.150.15.7up to date
 fastrace^0.70.7.14up to date
 fastrace-jaeger^0.70.7.14up to date
 libtest-mimic^0.80.8.1up to date
 opentelemetry^0.31.00.31.0up to date
 opentelemetry-otlp^0.31.00.31.0up to date
 opentelemetry_sdk^0.31.00.31.0up to date
 pretty_assertions^11.4.1up to date
 rand^0.80.9.2out of date
 sha2^0.100.10.9up to date
 size^0.50.5.0up to date
 tokio^1.481.48.0up to date
 tracing-opentelemetry^0.32.00.32.0up to date
 tracing-subscriber ⚠️^0.30.3.20maybe insecure

Security Vulnerabilities

sqlx: Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts

RUSTSEC-2024-0363

The following presentation at this year's DEF CON was brought to our attention on the SQLx Discord:

SQL Injection isn't Dead: Smuggling Queries at the Protocol Level
http://web.archive.org/web/20240812130923/https://media.defcon.org/DEF%20CON%2032/DEF%20CON%2032%20presentations/DEF%20CON%2032%20-%20Paul%20Gerste%20-%20SQL%20Injection%20Isn't%20Dead%20Smuggling%20Queries%20at%20the%20Protocol%20Level.pdf
(Archive link for posterity.)

Essentially, encoding a value larger than 4GiB can cause the length prefix in the protocol to overflow, causing the server to interpret the rest of the string as binary protocol commands or other data.

It appears SQLx does perform truncating casts in a way that could be problematic, for example: https://github.com/launchbadge/sqlx/blob/6f2905695b9606b5f51b40ce10af63ac9e696bb8/sqlx-postgres/src/arguments.rs#L163

This code has existed essentially since the beginning, so it is reasonable to assume that all published versions <= 0.8.0 are affected.

Mitigation

As always, you should make sure your application is validating untrustworthy user input. Reject any input over 4 GiB, or any input that could encode to a string longer than 4 GiB. Dynamically built queries are also potentially problematic if it pushes the message size over this 4 GiB bound.

Encode::size_hint() can be used for sanity checks, but do not assume that the size returned is accurate. For example, the Json<T> and Text<T> adapters have no reasonable way to predict or estimate the final encoded size, so they just return size_of::<T>() instead.

For web application backends, consider adding some middleware that limits the size of request bodies by default.

Resolution

sqlx 0.8.1 has been released with the fix: https://github.com/launchbadge/sqlx/blob/main/CHANGELOG.md#081---2024-08-23

Postgres users are advised to upgrade ASAP as a possible exploit has been demonstrated: https://github.com/launchbadge/sqlx/issues/3440#issuecomment-2307956901

MySQL and SQLite do not appear to be exploitable, but upgrading is recommended nonetheless.

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.