pyoxidizer 0.6.0

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 `pyoxidizer`

Dependencies

(39 total, 19 outdated, 2 possibly insecure)

Crate	Required	Latest	Status
anyhow	`^1.0`	`1.0.102`	up to date
byteorder	`^1.2`	`1.5.0`	up to date
cargo_toml	`^0.8`	`0.22.3`	out of date
cc	`^1.0`	`1.2.59`	up to date
clap	`^2.32`	`4.6.0`	out of date
codemap	`^0.1`	`0.1.3`	up to date
codemap-diagnostic	`^0.1`	`0.1.2`	up to date
copy_dir	`^0.1`	`0.1.3`	up to date
crc	`^1.8`	`3.4.0`	out of date
encoding_rs	`^0.8`	`0.8.35`	up to date
fs2	`^0.4`	`0.4.3`	up to date
git2	`^0.11`	`0.20.4`	out of date
glob	`^0.3`	`0.3.3`	up to date
goblin	`^0.2`	`0.10.5`	out of date
handlebars	`^2.0`	`6.4.0`	out of date
hex	`^0.4`	`0.4.3`	up to date
indoc	`^0.3`	`2.0.7`	out of date
itertools	`^0.8`	`0.14.0`	out of date
lazy_static	`^1.4`	`1.5.0`	up to date
libc	`^0.2`	`0.2.184`	up to date
path-dedot	`^1.1`	`3.1.1`	out of date
podio	`^0.1`	`0.2.0`	out of date
regex ⚠️	`^1`	`1.12.3`	maybe insecure
reqwest	`^0.9`	`0.13.2`	out of date
rustc_version	`^0.2`	`0.4.1`	out of date
semver	`^0.9`	`1.0.28`	out of date
serde	`^1.0`	`1.0.228`	up to date
serde_json	`^1.0`	`1.0.149`	up to date
sha2	`^0.8`	`0.11.0`	out of date
slog	`^2.4`	`2.8.2`	up to date
starlark	`^0.2`	`0.13.0`	out of date
tar ⚠️	`^0.4`	`0.4.45`	maybe insecure
tempdir	`^0.3`	`0.3.7`	up to date
url	`^2.1`	`2.5.8`	up to date
uuid	`^0.8`	`1.23.0`	out of date
version-compare	`^0.0`	`0.2.1`	out of date
walkdir	`^2`	`2.5.0`	up to date
zip	`^0.5`	`8.5.1`	out of date
zstd	`^0.5`	`0.13.3`	out of date

Dev dependencies

(1 total, 1 outdated)

Crate	Required	Latest	Status
indoc	`^0.3`	`2.0.7`	out of date

Security Vulnerabilities

`regex`: Regexes with large repetitions on empty sub-expressions take a very long time to parse

RUSTSEC-2022-0013

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

Overview

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.

Affected versions

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.

Mitigations

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.

Acknowledgements

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.

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