murphsicles / zorbs

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.

Crate `zorbs`

Dependencies

(28 total, 3 outdated, 2 possibly insecure)

Crate	Required	Latest	Status
axum	`^0.8.8`	`0.8.8`	up to date
tokio	`^1.49.0`	`1.50.0`	up to date
tower-http	`^0.6.8`	`0.6.8`	up to date
tracing	`^0.1.44`	`0.1.44`	up to date
tracing-subscriber	`^0.3.22`	`0.3.23`	up to date
serde	`^1.0.228`	`1.0.228`	up to date
serde_json	`^1.0.149`	`1.0.149`	up to date
dotenvy	`^0.15.7`	`0.15.7`	up to date
sqlx	`^0.8.6`	`0.8.6`	up to date
chrono	`^0.4.43`	`0.4.44`	up to date
uuid	`^1.21.0`	`1.22.0`	up to date
maud	`^0.27.0`	`0.27.0`	up to date
toml	`^1.0.3`	`1.1.0+spec-1.1.0`	up to date
tar ⚠️	`^0.4.44`	`0.4.45`	maybe insecure
flate2	`^1.1.9`	`1.1.9`	up to date
semver	`^1.0.27`	`1.0.27`	up to date
clap	`^4.5.59`	`4.6.0`	up to date
reqwest	`^0.12`	`0.13.2`	out of date
oauth2	`^5.0.0`	`5.0.0`	up to date
axum-login	`^0.18`	`0.18.0`	up to date
tower-sessions	`^0.14`	`0.15.0`	out of date
tower-sessions-sqlx-store	`^0.14`	`0.15.0`	out of date
time ⚠️	`^0.3`	`0.3.47`	maybe insecure
webauthn-rs	`^0.5.4`	`0.5.4`	up to date
url	`^2.5`	`2.5.8`	up to date
base64	`^0.22`	`0.22.1`	up to date
serde_cbor_2	`^0.13`	`0.13.0`	up to date
openssl-sys	`^0.9`	`0.9.112`	up to date

Security Vulnerabilities

`time`: Denial of Service via Stack Exhaustion

RUSTSEC-2026-0009

Impact

When 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.

Patches

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.

Workarounds

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 symlinks

RUSTSEC-2026-0067

In 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 nonzero

RUSTSEC-2026-0068

Versions 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.