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 test_integration

Dependencies

(6 total, 1 outdated)

CrateRequiredLatestStatus
 tempfile^3.3.03.14.0up to date
 owo-colors^3.5.04.1.0out of date
 clap^4.0.294.5.20up to date
 postgres^0.19.40.19.9up to date
 serde^1.0.1481.0.215up to date
 toml^0.8.20.8.19up to date

Crate test_codegen

Dependencies

(10 total, all up-to-date)

CrateRequiredLatestStatus
 futures^0.3.250.3.31up to date
 postgres^0.19.40.19.9up to date
 tokio-postgres^0.7.70.7.12up to date
 postgres-types^0.2.40.2.8up to date
 serde^1.0.1521.0.215up to date
 serde_json^1.0.911.0.132up to date
 time^0.3.170.3.36up to date
 uuid^1.2.21.11.0up to date
 eui48^1.1.01.1.0up to date
 rust_decimal^1.28.01.36.0up to date

Crate benches

Dependencies

(7 total, 1 possibly insecure)

CrateRequiredLatestStatus
 criterion^0.5.10.5.1up to date
 tokio^1.24.21.41.1up to date
 futures^0.3.250.3.31up to date
 postgres^0.19.40.19.9up to date
 tokio-postgres^0.7.70.7.12up to date
 postgres-types^0.2.40.2.8up to date
 diesel ⚠️^2.0.22.2.4maybe insecure

Crate cornucopia

Dependencies

(8 total, 3 outdated)

CrateRequiredLatestStatus
 postgres^0.19.40.19.9up to date
 postgres-types^0.2.40.2.8up to date
 thiserror^1.0.382.0.3out of date
 miette^5.5.07.2.0out of date
 chumsky^0.9.00.9.3up to date
 clap^4.1.14.5.20up to date
 heck^0.4.00.5.0out of date
 indexmap^2.0.22.6.0up to date

Crate cornucopia_sync

Dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 postgres^0.19.40.19.9up to date

Crate cornucopia_async

Dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 async-trait^0.1.630.1.83up to date
 tokio-postgres^0.7.70.7.12up to date
 deadpool-postgres^0.12.10.14.0out of date

Crate codegen_template

Dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 unscanny^0.1.00.1.0up to date
 unicode-xid^0.2.40.2.6up to date

Crate cornucopia_client_core

Dependencies

(5 total, 1 outdated)

CrateRequiredLatestStatus
 postgres-protocol^0.6.40.6.7up to date
 postgres-types^0.2.40.2.8up to date
 fallible-iterator^0.2.00.3.0out of date
 serde_json^1.0.911.0.132up to date
 serde^1.0.1521.0.215up to date

Security Vulnerabilities

diesel: Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts

RUSTSEC-2024-0365

The following presentation at this year's DEF CON was brought to our attention on the Diesel Gitter Channel:

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 Diesel does perform truncating casts in a way that could be problematic, for example: https://github.com/diesel-rs/diesel/blob/ae82c4a5a133db65612b7436356f549bfecda1c7/diesel/src/pg/connection/stmt/mod.rs#L36

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

Mitigation

The prefered migration to the outlined problem is to update to a Diesel version newer than 2.2.2, which includes fixes for the problem.

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.

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

Resolution

Diesel now uses #[deny] directives for the following Clippy lints:

to prevent casts that will lead to precision loss or other trunctations. Additionally we performed an audit of the relevant code.

A fix is included in the 2.2.3 release.