Deps.rs

alloy-primitives 1.1.2

[![dependency status](https://deps.rs/crate/alloy-primitives/1.1.2/status.svg)](https://deps.rs/crate/alloy-primitives/1.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 alloy-primitives

Dependencies

(27 total, 2 possibly insecure)

CrateRequiredLatestStatus
 allocative^0.3.20.3.4up to date
 alloy-rlp^0.30.3.12up to date
 arbitrary^1.31.4.1up to date
 bytes^11.10.1up to date
 cfg-if^1.0.01.0.0up to date
 derive_arbitrary^1.31.4.1up to date
 derive_more^2.02.0.1up to date
 diesel ⚠️^2.22.2.10maybe insecure
 foldhash^0.1.40.1.5up to date
 getrandom^0.30.3.3up to date
 hashbrown ⚠️^0.150.15.3maybe insecure
 const-hex^1.141.14.1up to date
 indexmap^2.52.9.0up to date
 itoa^11.0.15up to date
 k256^0.130.13.4up to date
 keccak-asm^0.1.00.1.4up to date
 paste^1.01.0.15up to date
 postgres-types^0.2.60.2.9up to date
 proptest^11.6.0up to date
 proptest-derive^0.50.5.1up to date
 rand^0.90.9.1up to date
 rayon^1.21.10.0up to date
 ruint^1.14.01.15.0up to date
 rustc-hash^2.12.1.1up to date
 serde^1.01.0.219up to date
 sha3^0.10.80.10.8up to date
 tiny-keccak^2.02.0.2up to date

Dev dependencies

(4 total, 2 outdated)

CrateRequiredLatestStatus
 bcs^0.1.60.1.6up to date
 bincode^1.32.0.1out of date
 criterion^0.50.6.0out of date
 serde_json^1.01.0.140up 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.

hashbrown: Borsh serialization of HashMap is non-canonical

RUSTSEC-2024-0402

The borsh serialization of the HashMap did not follow the borsh specification. It potentially produced non-canonical encodings dependent on insertion order. It also did not perform canonicty checks on decoding.

This can result in consensus splits and cause equivalent objects to be considered distinct.

This was patched in 0.15.1.