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.
torchbear(44 total, 27 outdated, 7 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix | ^0.7 | 0.13.5 | out of date |
| actix-lua | ^0.5 | 0.7.0 | out of date |
| actix-web ⚠️ | ^0.7 | 4.13.0 | out of date |
| base64 | ^0.10 | 0.22.1 | out of date |
| blake2 | ^0.8 | 0.10.6 | out of date |
| checksumdir | ^0.3.0 | 0.3.0 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.44 | maybe insecure |
| clap | ^2.32 | 4.6.0 | out of date |
| colored | ^1.6 | 3.1.1 | out of date |
| comrak ⚠️ | ^0.4 | 0.51.0 | out of date |
| diff-rs | ^0.2 | 0.2.3 | up to 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 |
| failure_derive | ^0.1 | 0.1.8 | up to date |
| fern | ^0.5 | 0.7.1 | out of date |
| futures | ^0.1 | 0.3.32 | out of date |
| git2 | ^0.8 | 0.20.4 | out of date |
| heck | ^0.3 | 0.5.0 | out of date |
| human-panic | ^1.0 | 2.0.6 | out of date |
| libm | ^0.1 | 0.2.16 | out of date |
| log | ^0.4 | 0.4.29 | up to date |
| mime_guess | ^1.8 | 2.0.5 | out of date |
| openssl ⚠️ | ^0.10 | 0.10.76 | maybe insecure |
| patch-rs | ^0.5 | 0.6.2 | out of date |
| regex ⚠️ | ^1.1 | 1.12.3 | maybe insecure |
| rlua | ^0.15 | 0.20.1 | out of date |
| rlua_serde | ^0.2 | 0.4.0 | out of date |
| scl | ^0.0 | 0.0.1 | up to date |
| select | ^0.4 | 0.6.1 | out of 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 |
| serde_yaml ⚠️ | ^0.8 | 0.9.34+deprecated | out of date |
| sodiumoxide | ^0.2 | 0.2.7 | up to date |
| splitdiff-rs | ^0.4 | 0.4.1 | up to date |
| tantivy | ^0.8 | 0.25.0 | out of date |
| tar ⚠️ | ^0.4 | 0.4.45 | maybe insecure |
| tera-v1 | ^1.0.0-alpha.4 | N/A | up to date |
| ulid | ^0.3 | 1.2.1 | out of date |
| uuid | ^0.7 | 1.22.0 | out of date |
| xz2 | ^0.1 | 0.1.7 | up to date |
| zip | ^0.5 | 8.4.0 | out of date |
(1 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| tempfile | ^3 | 3.27.0 | up to date |
serde_yaml: Uncontrolled recursion leads to abort in deserializationAffected versions of this crate did not properly check for recursion while deserializing aliases.
This allows an attacker to make a YAML file with an alias referring to itself causing an abort.
The flaw was corrected by checking the recursion depth.
actix-web: Multiple memory safety issuesAffected versions contain multiple memory safety issues, such as:
Send marker trait to objects that cannot be safely sent between threadsThis may result in a variety of memory corruption scenarios, most likely use-after-free.
A significant refactoring effort has been conducted to resolve these issues.
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.
comrak: XSS in `comrak`The comrak we were matching unsafe URL prefixes, such as data: or javascript: , in a case-sensitive manner. This meant prefixes like Data: were untouched.
comrak: XSS in `comrak`comrak operates by default in a "safe" mode of operation where unsafe content, such as arbitrary raw HTML or URLs with non-standard schemes, are not permitted in the output. This is per the reference GFM implementation, cmark-gfm.
Ampersands were not being correctly escaped in link targets, making it possible
to fashion unsafe URLs using schemes like data: or javascript: by entering
them as HTML entities, e.g. data:. The intended
behaviour, demonstrated upstream, is that these should be escaped and therefore
harmless, but this behaviour was broken in comrak.
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.
openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.
In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).
The maintainers thank quitbug for reporting this vulnerability to us.
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.