chore(deps): update dependency wolfi-dev/wolfictl to v0.38.23

[uniget-bot]

This PR contains the following updates:

Package	Update	Change
wolfi-dev/wolfictl	patch	0.38.22 -> 0.38.23

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

wolfi-dev/wolfictl (wolfi-dev/wolfictl)

v0.38.23

Compare Source

What's Changed

• build(deps): bump actions/checkout from 5.0.1 to 6.0.0 in /.github/actions by @​dependabot[bot] in #​1799
• build(deps): bump actions/checkout from 5.0.1 to 6.0.0 by @​dependabot[bot] in #​1798
• build(deps): bump golangci/golangci-lint-action from 8.0.0 to 9.1.0 by @​dependabot[bot] in #​1797
• build(deps): bump github.com/anchore/stereoscope from 0.1.9 to 0.1.13 by @​dependabot[bot] in #​1796
• build(deps): bump the chainguard group with 4 updates by @​dependabot[bot] in #​1795
• build(deps): bump github.com/containerd/containerd/v2 from 2.1.1 to 2.1.5 by @​dependabot[bot] in #​1784
• build(deps): bump step-security/harden-runner from 2.13.0 to 2.13.2 by @​dependabot[bot] in #​1783

Full Changelog: wolfi-dev/wolfictl@v0.38.22...v0.38.23

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[nicholasdille-bot]

Auto-approved because label type/renovate is present.

[github-actions]

🔍 Vulnerabilities of ghcr.io/uniget-org/tools/wolfictl:0.38.23

📦 Image Reference ghcr.io/uniget-org/tools/wolfictl:0.38.23

digest	sha256:823b87be430fed5c076230e8235e79852b84ccfa5ff37c37f07888f38dc1d528
vulnerabilities
platform	linux/amd64
size	51 MB
packages	330

github.com/u-root/u-root 0.15.0 (golang) pkg:golang/github.com/u-root/u-root@0.15.0 OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities Affected range <=v7.0.0 Fixed version Not Fixed CVSS Score 7.5 CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Description This affects all versions of package github.com/u-root/u-root/pkg/tarutil. It is vulnerable to both leading and non-leading relative path traversal attacks in tar file extraction. OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities Affected range <=7.0.0 Fixed version Not Fixed CVSS Score 7.5 CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Description This affects all versions of package github.com/u-root/u-root/pkg/uzip. It is vulnerable to both leading and non-leading relative path traversal attacks in zip file extraction.

github.com/anchore/grype 0.99.1 (golang) pkg:golang/github.com/anchore/grype@0.99.1 Improper Removal of Sensitive Information Before Storage or Transfer Affected range >=0.68.0 <0.104.1 Fixed version 0.104.1 CVSS Score 8.2 CVSS Vector CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N Description A credential disclosure vulnerability was found in Grype, affecting versions v0.68.0 through v0.104.0. If registry credentials are defined and the output of grype is written using the --file or --output json=<file> option, the registry credentials will be included unsanitized in the output file. Impact In Grype versions v0.68.0 through v0.104.0, when registry authentication is configured, those credentials can be incorrectly included in the output of a Grype scan (regardless of whether those credentials are actively being used for the current scan). Users that do not have registry authentication configured are not affected by this issue. Registry credentials can be set via the Grype configuration file (e.g. registry.auth[].username, registry.auth[].password, registry.auth[].token) or environment variables (e.g., GRYPE_REGISTRY_AUTH_USERNAME, GRYPE_REGISTRY_AUTH_PASSWORD, GRYPE_REGISTRY_AUTH_TOKEN). In order for the authentication details to be improperly included, the Grype file output format must be set to json with output target set to a file. For example --output json=file.json or --output json --file file.json. When these conditions are met, the configured credentials are not sanitized as they should be in the resulting JSON output file. The authentication details could also be leaked via a malformed Grype Template. A Grype Template that includes the Descriptor.Registry.Auth fields would also include the unsanitized registry credentials. There are no known templates that include these fields. Patches The patch has been released in v0.104.1. Workaround Users running affected versions of grype can work around this vulnerability by redirecting stdout to a file instead of using the --file or --output options. For example, replacing the command: # using `--output json=path` (or `--file`) leaks credentials grype --output json=test.json alpine:latest with # no use of `--output json=path` or `--file`. Output is sanitized... grype --output json alpine:latest > test.json ...results in the same test.json output, but the credentials will be properly sanitized. Resources Patch pull request: anchore/grype#3068

github.com/aws/aws-sdk-go 1.55.7 (golang) pkg:golang/github.com/aws/aws-sdk-go@1.55.7 Affected range >=0 Fixed version Not Fixed Description A padding oracle vulnerability exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. The SDK allows users to encrypt files with AES-CBC without computing a Message Authentication Code (MAC), which then allows an attacker who has write access to the target's S3 bucket and can observe whether or not an endpoint with access to the key can decrypt a file, they can reconstruct the plaintext with (on average) 128*length (plaintext) queries to the endpoint, by exploiting CBC's ability to manipulate the bytes of the next block and PKCS5 padding errors. It is recommended to update your SDK to V2 or later, and re-encrypt your files. Affected range >=0 Fixed version Not Fixed Description A vulnerability in the in-band key negotiation exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. An attacker with write access to the targeted bucket can change the encryption algorithm of an object in the bucket, which can then allow them to change AES-GCM to AES-CTR. Using this in combination with a decryption oracle can reveal the authentication key used by AES-GCM as decrypting the GMAC tag leaves the authentication key recoverable as an algebraic equation. It is recommended to update your SDK to V2 or later, and re-encrypt your files.

github.com/nwaples/rardecode/v2 2.1.1 (golang) pkg:golang/github.com/nwaples/rardecode/v2@2.1.1 Memory Allocation with Excessive Size Value Affected range <2.2.0 Fixed version 2.2.0 CVSS Score 5.3 CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L Description rardecode versions <= 2.1.1 fail to restrict the dictionary size when reading large RAR dictionary sizes, which allows an attacker to provide a specially crafted RAR file and cause Denial of Service via an Out Of Memory Crash.

github.com/nwaples/rardecode 1.1.3 (golang) pkg:golang/github.com/nwaples/rardecode@1.1.3 Affected range >=0 Fixed version Not Fixed Description DoS risk due to unrestricted RAR dictionary sizes in github.com/nwaples/rardecode

[github-actions]

Attempting automerge. See https://github.com/uniget-org/tools/actions/runs/19810130469.

[github-actions]

PR is clean and can be merged. See https://github.com/uniget-org/tools/actions/runs/19810130469.