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.38 | maybe insecure |
| chrono-humanize | ^0.0.11 | 0.2.3 | out of date |
| diesel ⚠️ | ^1.4.1 | 2.1.6 | out of date |
| diesel_migrations | ^1.4.0 | 2.1.0 | out of date |
| dotenv | ^0.13.0 | 0.15.0 | out of date |
| either | ^1.5.0 | 1.11.0 | up to date |
| failure | ^0.1.5 | 0.1.8 | up to date |
| fern | ^0.5.7 | 0.6.2 | out of date |
| futures | ^0.1.25 | 0.3.30 | out of date |
| hostname | ^0.1.5 | 0.4.0 | out of date |
| jsonwebtoken | ^5.0.1 | 9.3.0 | out of date |
| lazy_static | ^1.2.0 | 1.4.0 | up to date |
| lettre ⚠️ | ^0.8.3 | 0.11.7 | out of date |
| lettre_email | ^0.8.3 | 0.9.4 | out of date |
| log | ^0.4.6 | 0.4.21 | up to date |
| maplit | ^1.0.1 | 1.0.2 | up to date |
| native-tls | ^0.1.5 | 0.2.11 | out of date |
| packer | ^0.3.1 | 0.5.7 | out of date |
| serde | ^1.0.85 | 1.0.198 | up to date |
| serde_derive | ^1.0.85 | 1.0.198 | up to date |
| serde_json | ^1.0.37 | 1.0.116 | up to date |
| structopt | ^0.2.14 | 0.3.26 | out of date |
| syslog | ^4.0.1 | 6.1.1 | out of date |
| tera | ^0.11.20 | 1.19.1 | out of date |
| tokio ⚠️ | ^0.1.15 | 1.37.0 | out of date |
| tokio-threadpool | ^0.1.11 | 0.1.18 | up to date |
| uuid | ^0.6.5 | 1.8.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.
diesel: Fix a use-after-free bug in diesels Sqlite backendWe've misused sqlite3_column_name. The
SQLite documentation
states that the following:
The returned string pointer is valid until either the prepared statement is destroyed by sqlite3_finalize() or until the statement is automatically reprepared by the first call to sqlite3_step() for a particular run or until the next call to sqlite3_column_name() or sqlite3_column_name16() on the same column.
As part of our query_by_name infrastructure we've first received all
field names for the prepared statement and stored them as string slices
for later use. After that we called sqlite3_step() for the first time,
which invalids the pointer and therefore the stored string slice.
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.