Vulnerabilities

RUSTSEC-2024-0336

rustls::ConnectionCommon::complete_io could fall into an infinite loop based on network input

Details
Package	rustls
Version	0.20.9
URL	GHSA-6g7w-8wpp-frhj
Date	2024-04-19
Patched versions	>=0.23.5,>=0.22.4, <0.23.0,>=0.21.11, <0.22.0

If a close_notify alert is received during a handshake, complete_io
does not terminate.

Callers which do not call complete_io are not affected.

rustls-tokio and rustls-ffi do not call complete_io
and are not affected.

rustls::Stream and rustls::StreamOwned types use
complete_io and are affected.

RUSTSEC-2024-0363

Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts

Details
Package	sqlx
Version	0.6.3
URL	launchbadge/sqlx#3440
Date	2024-08-15
Patched versions	>=0.8.1

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&#39;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:
<launchbadge/sqlx#3440 (comment)>

MySQL and SQLite do not appear to be exploitable, but upgrading is recommended nonetheless.

Warnings

RUSTSEC-2022-0077

claim is Unmaintained

Details
Status	unmaintained
Package	claim
Version	0.5.0
URL	svartalf/rust-claim#12
Date	2022-12-04

The last release was in February 2021, almost two years ago.

The maintainer has been unresponsive regarding this crate for over a year.

A pending issue with claim's dependencies has made the crate difficult to use.

Possible Alternative(s)

The below list has not been vetted in any way and may or may not contain alternatives;

• claims, a direct fork of the claim crate

RUSTSEC-2024-0384

instant is unmaintained

Details
Status	unmaintained
Package	instant
Version	0.1.13
Date	2024-09-01

This crate is no longer maintained, and the author recommends using the maintained web-time crate instead.

RUSTSEC-2024-0320

yaml-rust is unmaintained.

Details
Status	unmaintained
Package	yaml-rust
Version	0.4.5
URL	rustsec/advisory-db#1921
Date	2024-03-20

The maintainer seems unreachable.

Many issues and pull requests have been submitted over the years
without any response.

Alternatives

Consider switching to the actively maintained yaml-rust2 fork of the original project:

• yaml-rust2
• yaml-rust2 @ crates.io