chore(deps): update dependency kubescape/kubescape to v4

[uniget-bot]

This PR contains the following updates:

Package	Update	Change
kubescape/kubescape	major	3.0.48 → 4.0.0

---

Warning

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

---

Release Notes

kubescape/kubescape (kubescape/kubescape)

v4.0.0

Compare Source

Changelog

• 01bb19b Add krew plugin manifest
• 2759bee Fix broken README anchors
• e0eeb69 Make version smoke test accept bytes and v-prefix
• 222c1ec Merge pull request #​1931 from Mujib-Ahasan/readmd-update
• 3b4585a Merge pull request #​1932 from kubescape/scan-images
• 427dcca Merge pull request #​1934 from kubescape/krew
• 8f009d4 Merge pull request #​1935 from kubescape/run_test_from_private_repo
• bd49251 Merge pull request #​1936 from kubescape/lint
• c0d4bb4 Merge pull request #​1937 from kubescape/dependabot/go_modules/github.com/theupdateframework/go-tuf/v2-2.4.1
• 0841d1d Merge pull request #​1939 from kubescape/feat/performance-optimization-phases-1-3
• 25bd51e Replace host sensor with node agent sensing (#​1916)
• 7f79bc2 Sort CVEs by severity then ID
• f70d81d add verbose option to scan-images
• dc49218 build(deps): Bump github.com/theupdateframework/go-tuf/v2
• 3623e55 feat: add image column to vulnerability scanning table output
• fbef268 feat: optimize CPU and memory usage for resource-intensive scans
• 57addd4 fix all linter errors
• b97f50f fix version handling and injection
• dc65bd4 force overridden ldflags in goreleaser
• 02790da remove invalid build flag
• 7c0e380 run system test from private repo
• aa9a610 run system test from private repo
• 2f7841b update policy.json testdata

---

Released by GoReleaser.

---

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/kubescape:4.0.0

📦 Image Reference ghcr.io/uniget-org/tools/kubescape:4.0.0

digest	sha256:4131a30a7878a00e9110aac31737df839ad4cce3260f944e1231874b0d8c8549
vulnerabilities
platform	linux/amd64
size	98 MB
packages	571

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.8 (golang) pkg:golang/github.com/aws/aws-sdk-go@1.55.8 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 1.1.3 (golang) pkg:golang/github.com/nwaples/rardecode@1.1.3 Memory Allocation with Excessive Size Value Affected range <=1.1.3 Fixed version Not Fixed 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-actions]

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

[github-actions]

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