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.
serwus(33 total, 12 outdated, 4 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix | ^0.13 | 0.13.5 | up to date |
| actix-cors | ^0.6 | 0.7.1 | out of date |
| actix-http | ^3 | 3.12.0 | up to date |
| actix-multipart | ^0.6 | 0.7.2 | out of date |
| actix-service | ^2 | 2.0.3 | up to date |
| actix-web | ^4 | 4.13.0 | up to date |
| alcoholic_jwt | ^1.0 | 4091.0.0 | out of date |
| awc | ^3 | 3.8.2 | up to date |
| bytes ⚠️ | ^1 | 1.11.1 | maybe insecure |
| chrono ⚠️ | ^0.4 | 0.4.44 | maybe insecure |
| colored | ^2.0 | 3.1.1 | out of date |
| derive_more | ^0.99 | 2.1.1 | out of date |
| diesel ⚠️ | ^2.1 | 2.3.7 | maybe insecure |
| diesel-derive-newtype | ^2.1 | 2.1.2 | up to date |
| dotenv | ^0.15 | 0.15.0 | up to date |
| futures | ^0.3 | 0.3.32 | up to date |
| jsonwebtoken | ^9 | 10.3.0 | out of date |
| log | ^0.4 | 0.4.29 | up to date |
| num_cpus | ^1 | 1.17.0 | up to date |
| paperclip | ^0.8 | 0.9.5 | out of date |
| quick-error | ^2 | 2.0.1 | up to date |
| r2d2 | ^0.8 | 0.8.10 | up to date |
| rand | ^0.8 | 0.10.0 | out of date |
| rust-argon2 | ^2 | 3.0.0 | out of date |
| serde | ^1 | 1.0.228 | up to date |
| serde_json | ^1 | 1.0.149 | up to date |
| serwus-derive | ^0.1.1 | 0.2.3 | out of date |
| tracing | ^0.1 | 0.1.44 | up to date |
| tracing-actix-web | ^0.7 | 0.7.21 | up to date |
| tracing-subscriber ⚠️ | ^0.3.16 | 0.3.23 | maybe insecure |
| validator | ^0.16 | 0.20.0 | out of date |
| validator_derive | ^0.16 | 0.20.0 | out of date |
| weighted-rs | ^0.1 | 0.1.3 | up to date |
chrono: Potential segfault in `localtime_r` invocationsUnix-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.
No workarounds are known.
diesel: Binary Protocol Misinterpretation caused by Truncating or Overflowing CastsThe 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.
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.
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.
tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequencesPrevious versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:
In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.
This was patched in PR #3368 to escape ANSI control characters from user input.
bytes: Integer overflow in `BytesMut::reserve`In the unique reclaim path of BytesMut::reserve, the condition
if v_capacity >= new_cap + offset
uses an unchecked addition. When new_cap + offset overflows usize in release builds, this condition may incorrectly pass, causing self.cap to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as spare_capacity_mut() then trust this corrupted cap value and may create out-of-bounds slices, leading to UB.
This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks.
use bytes::*;
fn main() {
let mut a = BytesMut::from(&b"hello world"[..]);
let mut b = a.split_off(5);
// Ensure b becomes the unique owner of the backing storage
drop(a);
// Trigger overflow in new_cap + offset inside reserve
b.reserve(usize::MAX - 6);
// This call relies on the corrupted cap and may cause UB & HBO
b.put_u8(b'h');
}
Users of BytesMut::reserve are only affected if integer overflow checks are configured to wrap. When integer overflow is configured to panic, this issue does not apply.