Deps.rs

opendal 0.51.0

[![dependency status](https://deps.rs/crate/opendal/0.51.0/status.svg)](https://deps.rs/crate/opendal/0.51.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

(68 total, 8 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.301.0.95up to date
 async-backtrace^0.2.60.2.7up to date
 async-tls^0.13.00.13.0up to date
 async-trait^0.1.680.1.83up to date
 atomic_lib^0.39.00.40.0out of date
 await-tree^0.20.2.1up to date
 backon^1.21.3.0up to date
 base64^0.220.22.1up to date
 bb8^0.80.9.0out of date
 bytes^1.61.9.0up to date
 cacache^13.013.1.0up to date
 chrono^0.4.280.4.39up to date
 compio^0.12.00.13.2out of 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.140.14.0up to date
 fastrace^0.7.10.7.4up to date
 flume^0.110.11.1up to date
 foundationdb^0.9.00.9.1up to date
 futures^0.30.3.31up to date
 getrandom^0.20.2.15up to date
 governor^0.6.00.8.0out of date
 hdfs-native^0.100.11.0out of date
 hdrs^0.3.20.3.2up to date
 hmac^0.12.10.12.1up to date
 hrana-client-proto^0.2.10.2.1up to date
 http^1.11.2.0up to date
 log^0.40.4.22up to date
 md-5^0.100.10.6up to date
 metrics^0.240.24.1up to date
 mime_guess^2.0.52.0.5up to date
 mini-moka^0.100.10.3up to date
 moka^0.120.12.8up to date
 mongodb^33.1.1up to date
 monoio^0.2.40.2.4up to date
 once_cell^11.20.2up to date
 openssh^0.11.00.11.4up to date
 openssh-sftp-client^0.15.20.15.2up to date
 opentelemetry^0.260.27.1out of date
 ouroboros^0.18.40.18.4up to date
 percent-encoding^22.3.1up to date
 persy^1.4.61.5.2up to date
 probe^0.5.10.5.1up to date
 prometheus^0.130.13.4up to date
 prometheus-client^0.22.20.22.3up to date
 prost^0.130.13.4up to date
 quick-xml^0.360.37.1out of date
 rand^0.80.8.5up to date
 redb^22.3.0up to date
 redis^0.270.27.6up to date
 reqsign^0.16.10.16.1up to date
 reqwest^0.12.20.12.10up to date
 rocksdb^0.21.00.23.0out of date
 rust-nebula^0.0.20.0.2up to date
 serde^11.0.216up to date
 serde_json^11.0.134up to date
 sha1^0.10.60.10.6up to date
 sha2^0.100.10.8up to date
 sled^0.34.70.34.7up to date
 snowflaked^11.0.3up to date
 sqlx ⚠️^0.8.00.8.2maybe insecure
 suppaftp^6.0.36.0.5up to date
 surrealdb^22.1.4up to date
 tikv-client^0.3.00.3.0up to date
 tokio^1.271.42.0up to date
 tracing^0.10.1.41up to date
 uuid^11.11.0up to date

Dev dependencies

(15 total, 4 outdated)

CrateRequiredLatestStatus
 criterion^0.50.5.1up to date
 dotenvy^0.150.15.7up to date
 fastrace^0.70.7.4up to date
 fastrace-jaeger^0.70.7.4up to date
 libtest-mimic^0.80.8.1up to date
 opentelemetry^0.260.27.1out of date
 opentelemetry-otlp^0.260.27.0out of date
 opentelemetry_sdk^0.260.27.1out of date
 pretty_assertions^11.4.1up to date
 rand^0.80.8.5up to date
 sha2^0.100.10.8up to date
 size^0.40.4.1up to date
 tokio^1.271.42.0up to date
 tracing-opentelemetry^0.27.00.28.0out of date
 tracing-subscriber^0.30.3.19up to date

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.