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 capp

Dependencies

(7 total, 1 possibly insecure)

CrateRequiredLatestStatus
 derive_builder^0.200.20.2up to date
 reqwest^0.120.12.15up to date
 rand^0.90.9.0up to date
 serde_yaml^0.90.9.34+deprecatedup to date
 rustis^0.130.13.3up to date
 mongodb^33.2.3up to date
 sqlx ⚠️^0.80.8.3maybe insecure

Dev dependencies

(10 total, all up-to-date)

CrateRequiredLatestStatus
 hyper^1.51.6.0up to date
 http-body-util^0.10.1.3up to date
 bytes^1.61.10.1up to date
 pin-project-lite^0.20.2.16up to date
 dotenvy^0.150.15.7up to date
 scraper^0.230.23.1up to date
 rand^0.90.9.0up to date
 md5^0.70.7.0up to date
 url^2.52.5.4up to date
 base64^0.220.22.1up to date

Crate capp-queue

Dependencies

(5 total, 1 possibly insecure)

CrateRequiredLatestStatus
 rustis^0.130.13.3up to date
 mongodb^33.2.3up to date
 futures^0.30.3.31up to date
 futures-util^0.30.3.31up to date
 sqlx ⚠️^0.80.8.3maybe insecure

Dev dependencies

(6 total, 1 outdated)

CrateRequiredLatestStatus
 dotenvy^0.150.15.7up to date
 tokio^1.431.44.1up to date
 serial_test^33.2.0up to date
 criterion^0.50.5.1up to date
 fake^3.0.14.2.0out of date
 mongodb^33.2.3up to date

Crate capp-config

Dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 backoff^0.40.4.0up to date
 serde_yaml^0.90.9.34+deprecatedup to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 tempfile^33.19.1up to date

Crate capp-router

Dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 url^2.52.5.4up to date
 indexmap^2.62.8.0up to date

Crate capp-cache

Dependencies

(3 total, 1 possibly insecure)

CrateRequiredLatestStatus
 chrono ⚠️^0.40.4.40maybe insecure
 bson^2.132.14.0up to date
 mongodb^33.2.3up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 dotenvy^0.150.15.7up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

Workarounds

No workarounds are known.

References

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.