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.
nihctfplat(29 total, 18 outdated, 5 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| antidote | ^1.0.0 | 1.0.0 | up to date |
| chrono ⚠️ | ^0.4.6 | 0.4.41 | maybe insecure |
| chrono-humanize | ^0.0.11 | 0.2.3 | out of date |
| diesel ⚠️ | ^1.4.1 | 2.2.12 | out of date |
| diesel_migrations | ^1.4.0 | 2.2.0 | out of date |
| dotenv | ^0.13.0 | 0.15.0 | out of date |
| either | ^1.5.0 | 1.15.0 | up to date |
| failure | ^0.1.5 | 0.1.8 | up to date |
| fern | ^0.5.7 | 0.7.1 | out of date |
| futures | ^0.1.25 | 0.3.31 | out of date |
| hostname | ^0.1.5 | 0.4.1 | out of date |
| jsonwebtoken | ^5.0.1 | 9.3.1 | out of date |
| lazy_static | ^1.2.0 | 1.5.0 | up to date |
| lettre ⚠️ | ^0.8.3 | 0.11.17 | out of date |
| lettre_email | ^0.8.3 | 0.9.4 | out of date |
| log | ^0.4.6 | 0.4.27 | up to date |
| maplit | ^1.0.1 | 1.0.2 | up to date |
| native-tls | ^0.1.5 | 0.2.14 | out of date |
| packer | ^0.3.1 | 0.5.7 | out of date |
| serde | ^1.0.85 | 1.0.219 | up to date |
| serde_derive | ^1.0.85 | 1.0.219 | up to date |
| serde_json | ^1.0.37 | 1.0.140 | up to date |
| structopt | ^0.2.14 | 0.3.26 | out of date |
| syslog | ^4.0.1 | 7.0.0 | out of date |
| tera | ^0.11.20 | 1.20.0 | out of date |
| tokio ⚠️ | ^0.1.15 | 1.46.1 | out of date |
| tokio-threadpool | ^0.1.11 | 0.1.18 | up to date |
| uuid | ^0.6.5 | 1.17.0 | out of date |
| warp ⚠️ | ^0.1.12 | 0.3.7 | out of 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.
lettre: SMTP command injection in bodyAffected versions of lettre allowed SMTP command injection through an attacker's controlled message body. The module for escaping lines starting with a period wouldn't catch a period that was placed after a double CRLF sequence, allowing the attacker to end the current message and write arbitrary SMTP commands after it.
The flaw is fixed by correctly handling consecutive CRLF sequences.
tokio: Data race when sending and receiving after closing a `oneshot` channelIf a tokio::sync::oneshot channel is closed (via the
oneshot::Receiver::close method), a data race may occur if the
oneshot::Sender::send method is called while the corresponding
oneshot::Receiver is awaited or calling try_recv.
When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.
Note that the race only occurs when both halves of the channel are used
after the Receiver half has called close. Code where close is not used, or where the
Receiver is not awaited and try_recv is not called after calling close,
is not affected.
See tokio#4225 for more details.
warp: Improper validation of Windows paths could lead to directory traversal attackPath resolution in warp::filters::fs::dir didn't correctly validate Windows paths
meaning paths like /foo/bar/c:/windows/web/screen/img101.png would be allowed
and respond with the contents of c:/windows/web/screen/img101.png. Thus users
could potentially read files anywhere on the filesystem.
This only impacts Windows. Linux and other unix likes are not impacted by this.
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.