Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency derailed/k9s to v0.40.2 #10344

Merged
merged 1 commit into from
Feb 17, 2025

Conversation

uniget-bot
Copy link

This PR contains the following updates:

Package Update Change
derailed/k9s patch 0.40.0 -> 0.40.2

Warning

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


Release Notes

derailed/k9s (derailed/k9s)

v0.40.2

Compare Source

Release v0.40.2

Notes

Thank you to all that contributed with flushing out issues and enhancements for K9s!
I'll try to mark some of these issues as fixed. But if you don't mind grab the latest rev
and see if we're happier with some of the fixes!
If you've filed an issue please help me verify and close.

Your support, kindness and awesome suggestions to make K9s better are, as ever, very much noted and appreciated!
Also big thanks to all that have allocated their own time to help others on both slack and on this repo!!

As you may know, K9s is not pimped out by corps with deep pockets, thus if you feel K9s is helping your Kubernetes journey,
please consider joining our sponsorship program and/or make some noise on social! @​kitesurfer

On Slack? Please join us K9slackers

Maintenance Release!

😳 Aye! Buzz kill on the 0.40.0 aftermath ;( Hot fix in progress...🙀 👻

Likely additional disturbance in the farce might be observed.
Thank you all for giving this drop a rinse and reporting back!! 😍


Videos Are In The Can!

Please dial K9s Channel for up coming content...


Resolved Issues

  • #​3116 Cannot list custom CRD's since v0.40.1

© 2024 Imhotep Software LLC. All materials licensed under Apache v2.0

v0.40.1

Compare Source

Release v0.40.1

Notes

Thank you to all that contributed with flushing out issues and enhancements for K9s!
I'll try to mark some of these issues as fixed. But if you don't mind grab the latest rev
and see if we're happier with some of the fixes!
If you've filed an issue please help me verify and close.

Your support, kindness and awesome suggestions to make K9s better are, as ever, very much noted and appreciated!
Also big thanks to all that have allocated their own time to help others on both slack and on this repo!!

As you may know, K9s is not pimped out by corps with deep pockets, thus if you feel K9s is helping your Kubernetes journey,
please consider joining our sponsorship program and/or make some noise on social! @​kitesurfer

On Slack? Please join us K9slackers

Maintenance Release!

😳 Aye! Buzz kill on the 0.40.0 aftermath... 🙀 👻

Likely additional disturbance in the farce might be observed.
Thank you all for giving v0.40.0 a rinse and reporting back!! 😍


Videos Are In The Can!

Please dial K9s Channel for up coming content...


Resolved Issues

  • #​3113 0.40.0 can't retain temporary view sort
  • #​3111 k9s can't describe or print YAML for HPAs in all namespaces view
  • #​2966 Go to the Contexts page and filter, contexts that are matched will be filtered ou
  • #​2962 Small colour/filtering related bug
  • #​2961 Drain node with the -disable-eviction
  • #​2958 Restart count in container view associated with the wrong container
  • #​2945 Could we add ServiceAccount Column in v1/POD view

Contributed PRs

Please be sure to give Big Thanks! and ATTA Girls/Boys! to all the fine contributors for making K9s better for all of us!!

  • #​3094 Log in as root to the node.
  • #​3033 Skip cache invalidation on failed connection
  • #​2965 Make menu foreground style configurable through skins
  • #​2952 A modest attempt to improve the logo aesthetics
  • #​2833 allow scaling custom resource
  • #​2799 feat(app): add history navigation with [ and ], most recent command with -
  • #​2719 fix: stop table header cells from being selectable
  • #​2865 Feature/DisableAutoscroll

© 2024 Imhotep Software LLC. All materials licensed under Apache v2.0


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.

Copy link

@nicholasdille-bot nicholasdille-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approved because label type/renovate is present.

Copy link

🔍 Vulnerabilities of ghcr.io/uniget-org/tools/k9s:0.40.2

📦 Image Reference ghcr.io/uniget-org/tools/k9s:0.40.2
digestsha256:2342a2c6db8fdee2cf9f90f9ee1a89fe08b88ecd3d97496b8ba4bb3fd65f9a90
vulnerabilitiescritical: 0 high: 0 medium: 5 low: 1
platformlinux/amd64
size36 MB
packages324
critical: 0 high: 0 medium: 3 low: 0 stdlib 1.23.2 (golang)

pkg:golang/[email protected]

medium : CVE--2024--45341

Affected range>=1.23.0-0
<1.23.5
Fixed version1.23.5
Description

A certificate with a URI which has a IPv6 address with a zone ID may incorrectly satisfy a URI name constraint that applies to the certificate chain.

Certificates containing URIs are not permitted in the web PKI, so this only affects users of private PKIs which make use of URIs.

medium : CVE--2024--45336

Affected range>=1.23.0-0
<1.23.5
Fixed version1.23.5
Description

The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com.

In the event that the client received a subsequent same-domain redirect, however, the sensitive headers would be restored. For example, a chain of redirects from a.com/, to b.com/1, and finally to b.com/2 would incorrectly send the Authorization header to b.com/2.

medium : CVE--2025--22866

Affected range>=1.23.0-0
<1.23.6
Fixed version1.23.6
Description

Due to the usage of a variable time instruction in the assembly implementation of an internal function, a small number of bits of secret scalars are leaked on the ppc64le architecture. Due to the way this function is used, we do not believe this leakage is enough to allow recovery of the private key when P-256 is used in any well known protocols.

critical: 0 high: 0 medium: 1 low: 1 github.com/aws/aws-sdk-go 1.44.288 (golang)

pkg:golang/github.com/aws/[email protected]

medium : CVE--2020--8911

Affected range>=0
Fixed versionNot 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.

low : CVE--2020--8912

Affected range>=0
Fixed versionNot 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.

critical: 0 high: 0 medium: 1 low: 0 k8s.io/apiserver 0.32.1 (golang)

pkg:golang/k8s.io/[email protected]

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.

Copy link

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

Copy link

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

@github-actions github-actions bot merged commit 935e14d into main Feb 17, 2025
10 checks passed
@github-actions github-actions bot deleted the renovate/derailed-k9s-0.40.x branch February 17, 2025 02:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants