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.
sn0int(48 total, 31 outdated, 6 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| atty | ^0.2 | 0.2.14 | up to date |
| base64 | ^0.10 | 0.22.1 | out of date |
| bufstream | ^0.1.4 | 0.1.4 | up to date |
| caps | ^0.3 | 0.5.6 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.44 | maybe insecure |
| chrootable-https | ^0.9 | 0.16.0 | out of date |
| colored | ^1.6 | 3.1.1 | out of date |
| crossbeam-channel | ^0.3 | 0.5.15 | out of date |
| ctrlc | ^3.1 | 3.5.2 | up to date |
| der-parser | ^1.1.0 | 10.0.0 | out of date |
| diesel ⚠️ | ^1.0.0 | 2.3.7 | out of date |
| diesel_migrations | ^1.3.0 | 2.3.1 | out of date |
| dirs | ^1.0 | 6.0.0 | out of date |
| env_logger | ^0.6 | 0.11.10 | out of date |
| failure | ^0.1 | 0.1.8 | up to date |
| hlua-badtouch | ^0.4 | 0.4.2 | up to date |
| kuchiki | ^0.7.2 | 0.8.1 | out of date |
| lazy_static | ^1.0 | 1.5.0 | up to date |
| libflate | ^0.1.14 | 2.2.1 | out of date |
| log | ^0.4 | 0.4.29 | up to date |
| maplit | ^1.0.1 | 1.0.2 | up to date |
| maxminddb ⚠️ | ^0.13 | 0.27.3 | out of date |
| nix | ^0.13 | 0.31.2 | out of date |
| nom | ^4.1.1 | 8.0.0 | out of date |
| opener | ^0.3.0 | 0.8.4 | out of date |
| pledge | ^0.3.1 | 0.4.2 | out of date |
| publicsuffix | ^1.5 | 2.3.0 | out of date |
| rand | ^0.6 | 0.10.0 | out of date |
| regex ⚠️ | ^1.0 | 1.12.3 | maybe insecure |
| rustyline | ^3 | 17.0.2 | out of date |
| semver | ^0.9 | 1.0.27 | out of date |
| separator | ^0.4 | 0.4.1 | up to date |
| serde | ^1.0 | 1.0.228 | up to date |
| serde_derive | ^1.0 | 1.0.228 | up to date |
| serde_json | ^1.0 | 1.0.149 | up to date |
| serde_urlencoded | ^0.5 | 0.7.1 | out of date |
| shellwords | ^1.0 | 1.1.0 | up to date |
| sloppy-rfc4880 | ^0.1.2 | 0.2.0 | out of date |
| sn0int-common | ^0.5.0 | 0.14.0 | out of date |
| structopt | ^0.2 | 0.3.26 | out of date |
| syscallz | ^0.11 | 0.17.0 | out of date |
| tar ⚠️ | ^0.4.17 | 0.4.45 | maybe insecure |
| threadpool | ^1.7 | 1.8.1 | up to date |
| tokio ⚠️ | ^0.1.14 | 1.50.0 | out of date |
| toml | ^0.4 | 1.1.0+spec-1.1.0 | out of date |
| unveil | ^0.2.0 | 0.3.2 | out of date |
| url | ^1.7 | 2.5.8 | out of date |
| x509-parser | ^0.4.0 | 0.18.1 | out of date |
(1 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| boxxy | ^0.9 | 0.14.0 | 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.
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.
regex: Regexes with large repetitions on empty sub-expressions take a very long time to parseThe Rust Security Response WG was notified that the regex crate did not
properly limit the complexity of the regular expressions (regex) it parses. An
attacker could use this security issue to perform a denial of service, by
sending a specially crafted regex to a service accepting untrusted regexes. No
known vulnerability is present when parsing untrusted input with trusted
regexes.
This issue has been assigned CVE-2022-24713. The severity of this vulnerability
is "high" when the regex crate is used to parse untrusted regexes. Other uses
of the regex crate are not affected by this vulnerability.
The regex crate features built-in mitigations to prevent denial of service
attacks caused by untrusted regexes, or untrusted input matched by trusted
regexes. Those (tunable) mitigations already provide sane defaults to prevent
attacks. This guarantee is documented and it's considered part of the crate's
API.
Unfortunately a bug was discovered in the mitigations designed to prevent untrusted regexes to take an arbitrary amount of time during parsing, and it's possible to craft regexes that bypass such mitigations. This makes it possible to perform denial of service attacks by sending specially crafted regexes to services accepting user-controlled, untrusted regexes.
All versions of the regex crate before or equal to 1.5.4 are affected by this
issue. The fix is include starting from regex 1.5.5.
We recommend everyone accepting user-controlled regexes to upgrade immediately
to the latest version of the regex crate.
Unfortunately there is no fixed set of problematic regexes, as there are practically infinite regexes that could be crafted to exploit this vulnerability. Because of this, we do not recommend denying known problematic regexes.
We want to thank Addison Crump for responsibly disclosing this to us according to the Rust security policy, and for helping review the fix.
We also want to thank Andrew Gallant for developing the fix, and Pietro Albini for coordinating the disclosure and writing this advisory.
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.
maxminddb: `Reader::open_mmap` unsoundly marks unsafe memmap operation as safemaxminddb prior to version 0.27 declared Reader::open_mmap as safe
despite wrapping an inherently unsafe memmap2 operation with no
extra step done to guarantee safety. This could have led to undefined
behaviour if the file were to be modified on disk while the memory map
was still active.
tar: `unpack_in` can chmod arbitrary directories by following symlinksIn versions 0.4.44 and below of tar-rs, when unpacking a tar archive, the tar
crate's unpack_dir function uses fs::metadata() to check
whether a path that already exists is a directory. Because fs::metadata()
follows symbolic links, a crafted tarball containing a symlink entry followed
by a directory entry with the same name causes the crate to treat the symlink
target as a valid existing directory — and subsequently apply chmod to it. This
allows an attacker to modify the permissions of arbitrary directories outside
the extraction root.
This issue has been fixed in version 0.4.45.
tar: tar-rs incorrectly ignores PAX size headers if header size is nonzeroVersions 0.4.44 and below of tar-rs have conditional logic that skips the PAX size header in cases where the base header size is nonzero.
As part of CVE-2025-62518, the astral-tokio-tar project was changed to correctly honor PAX size headers in the case where it was different from the base header. This is almost the inverse of the astral-tokio-tar issue.
Any discrepancy in how tar parsers honor file size can be used to create
archives that appear differently when unpacked by different archivers. In this
case, the tar-rs (Rust tar) crate is an outlier in checking for the header size
— other tar parsers (including e.g. Go archive/tar) unconditionally
use the PAX size override. This can affect anything that uses the tar crate to
parse archives and expects to have a consistent view with other parsers.
This issue has been fixed in version 0.4.45.