uniget-org / tools

Tool definitions for uniget
https://tools.uniget.dev
MIT License
2 stars 3 forks source link

chore(deps): update dependency eksctl-io/eksctl to v0.184.0 #5688

Closed uniget-bot closed 1 week ago

uniget-bot commented 1 week ago

This PR contains the following updates:

Package Update Change
eksctl-io/eksctl minor 0.183.0 -> 0.184.0

[!WARNING] Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

eksctl-io/eksctl (eksctl-io/eksctl) ### [`v0.184.0`](https://togithub.com/eksctl-io/eksctl/releases/tag/v0.184.0): eksctl 0.184.0 [Compare Source](https://togithub.com/eksctl-io/eksctl/compare/0.183.0...0.184.0) ### Release v0.184.0 #### 🚀 Features - Cluster creation flexibility for default networking addons ([#​7866](https://togithub.com/eksctl-io/eksctl/issues/7866)) #### 🎯 Improvements - use string in logging instead of wrapping error ([#​7838](https://togithub.com/eksctl-io/eksctl/issues/7838)) - Stop using P2 instances which will be retired ([#​7826](https://togithub.com/eksctl-io/eksctl/issues/7826)) #### 🧰 Maintenance - Fix SDK paginator mocks ([#​7850](https://togithub.com/eksctl-io/eksctl/issues/7850)) - Schedule pods on a nodegroup on which no concurrent actions are executed ([#​7834](https://togithub.com/eksctl-io/eksctl/issues/7834)) #### Acknowledgments The eksctl maintainers would like to sincerely thank [@​moreandres](https://togithub.com/moreandres).

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.



This PR has been generated by Renovate Bot.

github-actions[bot] commented 1 week ago

:mag: Vulnerabilities of ghcr.io/uniget-org/tools/eksctl:0.184.0

:package: Image Reference ghcr.io/uniget-org/tools/eksctl:0.184.0
digestsha256:5f58a6490e3d466eb084ff957dce31fc7f6df340c1a966b3cee4505f8deabfb7
vulnerabilitiescritical: 0 high: 0 medium: 2 low: 1 unspecified: 1
platformlinux/amd64
size36 MB
packages238
critical: 0 high: 0 medium: 1 low: 1 github.com/aws/aws-sdk-go 1.51.16 (golang) pkg:golang/github.com/aws/aws-sdk-go@1.51.16
medium : CVE--2020--8911
Affected range>=0
Fixed versionNot Fixed
Description
The Go AWS S3 Crypto SDK contains vulnerabilities that can permit an attacker with write access to a bucket to decrypt files in that bucket. Files encrypted by the V1 EncryptionClient using either the AES-CBC content cipher or the KMS key wrap algorithm are vulnerable. Users should migrate to the V1 EncryptionClientV2 API, which will not create vulnerable files. Old files will remain vulnerable until re-encrypted with the new client.
low : CVE--2020--8912
Affected range>=0
Fixed versionNot Fixed
Description
The Go AWS S3 Crypto SDK contains vulnerabilities that can permit an attacker with write access to a bucket to decrypt files in that bucket. Files encrypted by the V1 EncryptionClient using either the AES-CBC content cipher or the KMS key wrap algorithm are vulnerable. Users should migrate to the V1 EncryptionClientV2 API, which will not create vulnerable files. Old files will remain vulnerable until re-encrypted with the new client.
critical: 0 high: 0 medium: 1 low: 0 k8s.io/apiserver 0.29.0 (golang) pkg:golang/k8s.io/apiserver@0.29.0
medium 4.3: CVE--2020--8552 OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities
Affected range<1.15.10
Fixed version1.15.10, 1.16.7, 1.17.3
CVSS Score4.3
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
Description
The Kubernetes API server component has been found to be vulnerable to a denial of service attack via successful API requests.
critical: 0 high: 0 medium: 0 low: 0 unspecified: 1stdlib 1.21.11 (golang) pkg:golang/stdlib@1.21.11
unspecified : CVE--2024--24791
Affected range<1.21.12
Fixed version1.21.12
Description
The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next request sent on the connection will fail. An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending "Expect: 100-continue" requests which elicit a non-informational response from the backend. Each such request leaves the proxy with an invalid connection, and causes one subsequent request using that connection to fail.
github-actions[bot] commented 1 week ago

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

github-actions[bot] commented 1 week ago

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