chore(deps): update dependency kubescape/kubescape to v3.0.48

[uniget-bot]

This PR contains the following updates:

Package	Update	Change
kubescape/kubescape	patch	3.0.47 → 3.0.48

---

Warning

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

---

Release Notes

kubescape/kubescape (kubescape/kubescape)

v3.0.48

Compare Source

Changelog

• 3f3681a Add SkipPersistence flag to MetricsQueryParams in metrics endpoint
• 32a15ac Add test for CheckShortTerminalWidth with non-string values
• 7ca609d Complete fix for workload scan missing controls
• c32e665 Final verification - all changes complete
• 82ec11b Fix indentation in test file
• 0e4ff13 Fix typos in documentation
• 837a50c Fix unsafe interface to string type assertions to prevent panic
• ea12643 Fix workflow YAML formatting and permissions
• 872c0c9 Fix workload scan to include allcontrols framework
• bd00d15 Initial plan
• 9353eb5 Initial plan
• 1225540 Merge pull request #​1913 from oglok/fix-typos-in-docs
• 3b6bc00 Merge pull request #​1914 from majiayu000/fix-1617-kustomize-directory-analysis-n-1231-0603
• d6ccc37 Merge pull request #​1915 from majiayu000/fix-1660-define-labels-to-copy-from-wor-1231-0603
• 423d9c5 Merge pull request #​1917 from BroderPeters/master
• 9d876b1 Merge pull request #​1918 from AndrewCharlesHay/patch-1
• 9445e0a Merge pull request #​1920 from kubescape/dependabot/go_modules/github.com/sigstore/cosign/v3-3.0.4
• aa62fbe Merge pull request #​1921 from kubescape/buildnumber
• 4d3b3ef Merge pull request #​1922 from kubescape/copilot/fix-kubescape-report-discrepancy
• 3060500 Merge pull request #​1923 from kubescape/dependabot/go_modules/github.com/sigstore/fulcio-1.8.5
• 0cf24d0 Merge pull request #​1926 from kubescape/copilot/fix-kubescan-interface-error
• 09aa1ab Merge pull request #​1927 from kubescape/dependabot/go_modules/github.com/theupdateframework/go-tuf/v2-2.3.1
• 6ce0121 Merge pull request #​1928 from kubescape/dependabot/go_modules/github.com/sigstore/rekor-1.5.0
• 8984f94 Update README to include GoReleaser installation and usage instructions
• 75fb07e Update build number retrieval and permissions in workflow
• 08d964b Update golangci-lint action to version 9
• 0c42b41 build(deps): Bump github.com/sigstore/cosign/v3
• 413db87 build(deps): Bump github.com/sigstore/fulcio from 1.8.4 to 1.8.5
• 0ec188b build(deps): Bump github.com/sigstore/rekor from 1.4.3 to 1.5.0
• 090820b build(deps): Bump github.com/theupdateframework/go-tuf/v2
• 8952336 ci: update scorecard action version
• 46eb266 feat: add labels-to-copy flag to copy workload labels to reports
• 0f21258 fix: enable kustomize overlays to load base configurations
• 351f957 update test lists (#​1919)

---

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.

[github-actions]

🔍 Vulnerabilities of ghcr.io/uniget-org/tools/kubescape:3.0.48

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

digest	sha256:0af28a88c36929f5ff3d092567ef91c3717dafa5257e40872daa787c539354cf
vulnerabilities
platform	linux/amd64
size	53 MB
packages	570

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/sigstore/sigstore 1.10.3 (golang) pkg:golang/github.com/sigstore/sigstore@1.10.3 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') Affected range <=1.10.3 Fixed version 1.10.4 CVSS Score 5.8 CVSS Vector CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N Description Summary The legacy TUF client pkg/tuf/client.go, which supports caching target files to disk, constructs a filesystem path by joining a cache base directory with a target name sourced from signed target metadata, but it does not validate that the resulting path stays within the cache base directory. Note that this should only affect clients that are directly using the TUF client in sigstore/sigstore or are using an older version of Cosign. As this TUF client implementation is deprecated, users should migrate to https://github.com/sigstore/sigstore-go/tree/main/pkg/tuf as soon as possible. Note that this does not affect users of the public Sigstore deployment, where TUF metadata is validated by a quorum of trusted collaborators. Impact A malicious TUF repository can trigger arbitrary file overwriting, limited to the permissions that the calling process has. Workarounds Users can disable disk caching for the legacy client by setting SIGSTORE_NO_CACHE=true in the environment, migrate to https://github.com/sigstore/sigstore-go/tree/main/pkg/tuf, or upgrade to the latest sigstore/sigstore release.

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.