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.
cargo(70 total, 22 outdated, 4 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| annotate-snippets | ^0.11.2 | 0.12.13 | out of date |
| anstream | ^0.6.13 | 1.0.0 | out of date |
| anstyle | ^1.0.6 | 1.0.14 | up to date |
| anyhow | ^1.0.82 | 1.0.102 | up to date |
| base64 | ^0.22.1 | 0.22.1 | up to date |
| bytesize | ^1.3 | 2.3.1 | out of date |
| cargo-credential | ^0.4.2 | 0.4.9 | up to date |
| cargo-credential-libsecret | ^0.4.7 | 0.5.5 | out of date |
| cargo-credential-macos-keychain | ^0.4.7 | 0.4.20 | up to date |
| cargo-credential-wincred | ^0.4.7 | 0.4.20 | up to date |
| cargo-platform | ^0.1.5 | 0.3.2 | out of date |
| cargo-util | ^0.2.14 | 0.2.27 | up to date |
| cargo-util-schemas | ^0.5.0 | 0.12.0 | out of date |
| clap | ^4.5.4 | 4.6.0 | up to date |
| color-print | ^0.3.6 | 0.3.7 | up to date |
| crates-io | ^0.40.4 | 0.40.17 | up to date |
| curl | ^0.4.46 | 0.4.49 | up to date |
| curl-sys | ^0.4.72 | 0.4.87+curl-8.19.0 | up to date |
| filetime | ^0.2.23 | 0.2.27 | up to date |
| flate2 | ^1.0.30 | 1.1.9 | up to date |
| git2 | ^0.19.0 | 0.20.4 | out of date |
| git2-curl | ^0.20.0 | 0.21.0 | out of date |
| gix | ^0.64.0 | 0.81.0 | out of date |
| glob | ^0.3.1 | 0.3.3 | up to date |
| hex | ^0.4.3 | 0.4.3 | up to date |
| hmac | ^0.12.1 | 0.13.0 | out of date |
| home | ^0.5.9 | 0.5.12 | up to date |
| http-auth | ^0.1.9 | 0.1.10 | up to date |
| humantime | ^2.1.0 | 2.3.0 | up to date |
| ignore | ^0.4.22 | 0.4.25 | up to date |
| im-rc | ^15.1.0 | 15.1.0 | up to date |
| indexmap | ^2.2.6 | 2.13.0 | up to date |
| itertools | ^0.13.0 | 0.14.0 | out of date |
| jobserver | ^0.1.28 | 0.1.34 | up to date |
| lazycell | ^1.3.0 | 1.3.0 | up to date |
| libc | ^0.2.154 | 0.2.184 | up to date |
| libgit2-sys | ^0.17.0 | 0.18.3+1.9.2 | out of date |
| memchr | ^2.7.2 | 2.8.0 | up to date |
| opener | ^0.7.0 | 0.8.4 | out of date |
| openssl ⚠️ | ^0.10.57 | 0.10.76 | maybe insecure |
| os_info | ^3.8.2 | 3.14.0 | up to date |
| pasetors | ^0.6.8 | 0.7.8 | out of date |
| pathdiff | ^0.2.1 | 0.2.3 | up to date |
| rand | ^0.8.5 | 0.10.0 | out of date |
| regex | ^1.10.4 | 1.12.3 | up to date |
| rusqlite | ^0.31.0 | 0.39.0 | out of date |
| rustfix | ^0.8.2 | 0.9.4 | out of date |
| same-file | ^1.0.6 | 1.0.6 | up to date |
| semver | ^1.0.22 | 1.0.27 | up to date |
| serde | ^1.0.199 | 1.0.228 | up to date |
| serde-untagged | ^0.1.5 | 0.1.9 | up to date |
| serde_ignored | ^0.1.10 | 0.1.14 | up to date |
| serde_json | ^1.0.116 | 1.0.149 | up to date |
| sha1 | ^0.10.6 | 0.11.0 | out of date |
| shell-escape | ^0.1.5 | 0.1.5 | up to date |
| supports-hyperlinks | ^3.0.0 | 3.2.0 | up to date |
| supports-unicode | ^3.0.0 | 3.0.0 | up to date |
| tar ⚠️ | ^0.4.40 | 0.4.45 | maybe insecure |
| tempfile | ^3.10.1 | 3.27.0 | up to date |
| time ⚠️ | ^0.3.36 | 0.3.47 | maybe insecure |
| toml | ^0.8.14 | 1.1.2+spec-1.1.0 | out of date |
| toml_edit | ^0.22.14 | 0.25.10+spec-1.1.0 | out of date |
| tracing | ^0.1.40 | 0.1.44 | up to date |
| tracing-chrome | ^0.7.2 | 0.7.2 | up to date |
| tracing-subscriber ⚠️ | ^0.3.18 | 0.3.23 | maybe insecure |
| unicase | ^2.7.0 | 2.9.0 | up to date |
| unicode-width | ^0.1.12 | 0.2.2 | out of date |
| url | ^2.5.0 | 2.5.8 | up to date |
| walkdir | ^2.5.0 | 2.5.0 | up to date |
| windows-sys | ^0.52 | 0.61.2 | out of date |
(5 total, 4 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| annotate-snippets | ^0.11.2 | 0.12.13 | out of date |
| cargo-test-support | ^0.3.0 | 0.10.0 | out of date |
| gix | ^0.64.0 | 0.81.0 | out of date |
| same-file | ^1.0.6 | 1.0.6 | up to date |
| snapbox | ^0.6.9 | 1.2.0 | out of date |
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.
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.
time: Denial of Service via Stack ExhaustionWhen user-provided input is provided to any type that parses with the RFC 2822 format, a denial of service attack via stack exhaustion is possible. The attack relies on formally deprecated and rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary, non-malicious input will never encounter this scenario.
A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned rather than exhausting the stack.
Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of the stack consumed would be at most a factor of the length of the input.
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.