Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

URL has been copied successfully!
Critical RCE flaws put Kubernetes clusters at risk of takeover
URL has been copied successfully!

Collecting Cyber-News from over 60 sources

Critical RCE flaws put Kubernetes clusters at risk of takeover

Two ways to mitigate the flaws: The best fix is to upgrade the Ingress-NGINX component to one of the patched versions. Admins can determine if it’s being used inside their clusters by typing: kubectl get pods all-namespaces selector app.kubernetes.io/name=ingress-nginxIn situations where an immediate version upgrade is not possible, admins can reduce risk by deleting the ValidatingWebhookConfiguration called ingress-nginx-admission and remove the validating-webhook argument from the ingress-nginx-controller container’s Deployment or DaemonSet. If ingress-nginx was installed using Helm, it can be reinstalled with controller.admissionWebhooks.enabled=false.This will mitigate CVE-2025-1974 in particular, which makes it much easier to exploit the other vulnerabilities without authentication. However, the Validating Admission Controller should not remain disabled for a long time because it provides safeguards against bad ingress configurations to legitimate users.


First seen on csoonline.com

Jump to article: www.csoonline.com/article/3854089/critical-rce-flaws-put-kubernetes-clusters-at-risk-of-takeover.html

Loading

Share via Email
Share on Facebook
Tweet on X (Twitter)
Share on Whatsapp
Share on LinkedIn
Share on Xing
Copy link