Deps.rs

poem-openapi 5.1.2

[![dependency status](https://deps.rs/crate/poem-openapi/5.1.2/status.svg)](https://deps.rs/crate/poem-openapi/5.1.2)

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 poem-openapi

Dependencies

(31 total, 1 possibly insecure)

CrateRequiredLatestStatus
 base64^0.22.00.22.1up to date
 bson^2.0.02.13.0up to date
 bytes^1.1.01.7.2up to date
 chrono^0.4.310.4.38up to date
 derive_more^1.01.0.0up to date
 email_address^0.2.10.2.9up to date
 futures-util^0.3.170.3.31up to date
 geo-types^0.7.120.7.13up to date
 geojson^0.24.10.24.1up to date
 hostname-validator^1.1.01.1.1up to date
 humantime^2.1.02.1.0up to date
 indexmap^2.0.02.6.0up to date
 ipnet^2.7.12.10.1up to date
 mime^0.3.160.3.17up to date
 num-traits^0.2.140.2.19up to date
 poem^3.1.03.1.1up to date
 poem-openapi-derive^5.1.15.1.1up to date
 prost-wkt-types^0.6.00.6.0up to date
 quick-xml^0.36.10.36.2up to date
 regex^1.5.51.11.0up to date
 rust_decimal^1.22.01.36.0up to date
 serde^1.0.1301.0.210up to date
 serde_json^1.0.681.0.129up to date
 serde_urlencoded^0.7.10.7.1up to date
 serde_yaml^0.90.9.34+deprecatedup to date
 sqlx ⚠️^0.8.00.8.2maybe insecure
 thiserror^1.0.301.0.64up to date
 time^0.3.360.3.36up to date
 tokio^1.39.11.40.0up to date
 url^2.2.22.5.2up to date
 uuid^1.1.01.11.0up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 poem^3.1.03.1.1up to date
 tokio^1.39.11.40.0up 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.