Deps.rs

njupt-nyr / sopt

[![dependency status](https://deps.rs/repo/github/njupt-nyr/sopt/status.svg)](https://deps.rs/repo/github/njupt-nyr/sopt)

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

Crate sopt

Dependencies

(35 total, 14 outdated, 2 insecure)

CrateRequiredLatestStatus
 actix-multipart^0.6.00.8.5out of date
 actix-web^4.3.14.15.0up to date
 csv^1.2.21.4.0up to date
 rocksdb^0.21.00.25.0out of date
 sled^0.34.70.34.7up to date
 sqlx ⚠️^0.7.00.9.0insecure
 tokio^1.291.53.2up to date
 serde^11.0.229up to date
 serde_bencode*0.2.4up to date
 serde_bytes*0.11.19up to date
 serde_json*1.0.152up to date
 serde_qs*1.1.3up to date
 aws-config^0.55.31.12.0out of date
 aws-sdk-s3^0.28.01.152.0out of date
 aws-smithy-http^0.55.30.64.1out of date
 cfg-if^1.01.0.5up to date
 chrono^0.4.260.4.45up to date
 config^0.13.30.15.27out of date
 dotenv*0.15.0up to date
 log4rs^11.4.0up to date
 futures^0.3.280.3.34up to date
 hex*0.4.3up to date
 jsonwebtoken^811.1.0out of date
 lazy_static*1.5.1up to date
 lettre ⚠️^0.10.40.11.23insecure
 pest*2.9.3up to date
 pest_derive*2.9.3up to date
 reqwest^0.110.13.5out of date
 sanitize-filename*0.6.0up to date
 strsim*0.11.1up to date
 base64^0.21.20.23.1out of date
 rand^0.8.50.10.3out of date
 rust-argon2^1.03.0.0out of date
 sha-1^0.100.10.1up to date
 sha2^0.100.11.0out of date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 cargo-husky^11.5.0up to date

Crate sopt_proxy

Dependencies

(15 total, 5 outdated, 1 insecure)

CrateRequiredLatestStatus
 serde^11.0.229up to date
 actix-web^44.15.0up to date
 sqlx ⚠️^0.7.00.9.0insecure
 deadpool^0.90.13.1out of date
 deadpool-redis^0.12.00.23.1out of date
 bendy*0.6.1up to date
 bloom^0.3.20.3.2up to date
 tokio^1.291.53.2up to date
 config^0.13.30.15.27out of date
 dotenv*0.15.0up to date
 serde_qs*1.1.3up to date
 lazy_static*1.5.1up to date
 reqwest^0.110.13.5out of date
 hex*0.4.3up to date
 log4rs^11.4.0up to date

Crate sopt_tracker

Dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 indexmap^22.14.2up to date
 rand^0.8.30.10.3out of date

Crate sopt_derive

Dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 syn^23.0.7out 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.

lettre: TLS hostname verification disabled when using Boring TLS backend

RUSTSEC-2026-0141

An inverted-boolean bug in lettre's boring-tls integration silently disables TLS hostname verification for callers using the default (strict) configuration. An on-path attacker presenting any chain-valid certificate for any domain can intercept SMTP submission, including PLAIN/LOGIN credentials and message contents, against any lettre user built with the boring-tls feature. Other TLS backends (native-tls, rustls) are unaffected.

The bug was introduced in v0.10.1 and persists through v0.11.21 (latest).