Deps.rs

forgeflux-org / starchart

[![dependency status](https://deps.rs/repo/github/forgeflux-org/starchart/status.svg)](https://deps.rs/repo/github/forgeflux-org/starchart)

This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate starchart

Dependencies

(27 total, 13 outdated, 1 insecure)

CrateRequiredLatestStatus
 actix-rt^2.72.15.0up to date
 actix-web^4.0.14.15.0up to date
 actix-identity^0.4.00.9.0out of date
 actix-files^0.6.00.7.0out of date
 async-trait^0.1.510.1.92up to date
 config^0.13.00.15.25out of date
 lazy_static^1.4.01.5.0up to date
 mime^0.3.160.3.17up to date
 mime_guess^2.0.32.0.5up to date
 rand^0.8.50.10.2out of date
 tera^1.152.4.0out of date
 tokio^1.171.53.1up to date
 url^2.2.22.5.8up to date
 validator^0.150.21.0out of date
 derive_more^0.99.172.1.1out of date
 log^0.4.160.4.34up to date
 pretty_env_logger^0.40.5.0out of date
 rust-embed^6.3.08.12.0out of date
 urlencoding^2.1.02.1.3up to date
 clap^4.0.324.6.7up to date
 actix^0.13.00.13.5up to date
 derive_builder^0.12.00.20.2out of date
 reqwest^0.11.100.13.5out of date
 serde^11.0.229up to date
 serde_json^11.0.151up to date
 trust-dns-resolver^0.21.10.23.2out of date
 sqlx ⚠️^0.6.20.9.0insecure

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 mktemp^0.4.10.5.1out of date

Crate api_routes

Dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 serde^11.0.229up to date

Crate db-core

Dependencies

(4 total, 1 outdated)

CrateRequiredLatestStatus
 async-trait^0.1.510.1.92up to date
 thiserror^1.0.302.0.20out of date
 serde^11.0.229up to date
 url^2.2.22.5.8up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 serde_json^11.0.151up to date

Crate db-sqlx-sqlite

Dependencies

(3 total, 1 outdated, 1 insecure)

CrateRequiredLatestStatus
 sqlx ⚠️^0.6.20.9.0insecure
 async-trait^0.1.510.1.92up to date
 url^2.2.22.5.8up to date

Dev dependencies

(3 total, 1 outdated, 1 insecure)

CrateRequiredLatestStatus
 actix-rt^22.15.0up to date
 sqlx ⚠️^0.6.20.9.0insecure
 url^2.2.22.5.8up to date

Crate gitea

Dependencies

(6 total, 1 outdated)

CrateRequiredLatestStatus
 async-trait^0.1.510.1.92up to date
 url^2.2.22.5.8up to date
 tokio^1.171.53.1up to date
 reqwest^0.11.100.13.5out of date
 serde^11.0.229up to date
 serde_json^11.0.151up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 actix-rt^2.72.15.0up to date

Crate forge-core

Dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 async-trait^0.1.510.1.92up to date
 url^2.2.22.5.8up to date

Crate federate-core

Dependencies

(5 total, 2 outdated)

CrateRequiredLatestStatus
 async-trait^0.1.510.1.92up to date
 thiserror^1.0.302.0.20out of date
 serde^11.0.229up to date
 url^2.2.22.5.8up to date
 reqwest^0.11.100.13.5out of date

Crate publiccodeyml

Dependencies

(10 total, 3 outdated)

CrateRequiredLatestStatus
 async-trait^0.1.510.1.92up to date
 serde^11.0.229up to date
 serde_yaml^0.90.9.34+deprecatedup to date
 tokio^1.18.21.53.1up to date
 thiserror^1.0.302.0.20out of date
 url^2.2.22.5.8up to date
 tar^0.4.380.4.46up to date
 log^0.4.160.4.34up to date
 mktemp^0.4.10.5.1out of date
 reqwest^0.11.100.13.5out of date

Dev dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 actix-rt^22.15.0up to date
 mktemp^0.4.10.5.1out 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.