Deps.rs

geozero 0.14.0

[![dependency status](https://deps.rs/crate/geozero/0.14.0/status.svg)](https://deps.rs/crate/geozero/0.14.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 geozero

Dependencies

(21 total, 10 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 byteorder^1.4.31.5.0up to date
 bytes^1.41.10.1up to date
 csv^1.2.21.3.1up to date
 dbase^0.40.6.0out of date
 diesel^2.2.32.2.11up to date
 dup-indexer^0.30.4.3out of date
 gdal^0.160.18.0out of date
 gdal-sys^0.90.11.0out of date
 geo-types^0.7.110.7.16up to date
 geojson^0.24.10.24.2up to date
 geos^9.010.0.0out of date
 gpx^0.90.10.0out of date
 log^0.4.190.4.27up to date
 lyon^1.0.11.0.1up to date
 postgres-types^0.20.2.9up to date
 prost^0.11.90.14.1out of date
 scroll^0.110.13.0out of date
 serde_json^1.0.1041.0.140up to date
 sqlx ⚠️^0.80.8.6maybe insecure
 thiserror^1.02.0.12out of date
 wkt^0.110.14.0out of date

Dev dependencies

(8 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 geo^0.26.00.30.0out of date
 hex^0.40.4.3up to date
 kdbush^0.20.2.0up to date
 postgres^0.190.19.10up to date
 seek_bufread^1.21.2.2up to date
 sqlx ⚠️^0.80.8.6maybe insecure
 tokio^1.30.01.46.0up to date
 wkt^0.110.14.0out of 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.