Upgrading Nginx-Ingress did not go smoothly today

It worked, but I had to deviate from the recommended steps - without really having time to figure out why.

My Notes here

https://tangiblebytes.co.uk/2025/kubernetes-nginx-ingress-cve-2025-1974/

#kubernetes #nginx #CVE_2025_1974 #helm

Kubernetes Nginx Ingress Cve 2025 1974

There is a fairly severe bug here Ingress-nginx CVE-2025-1974 My understanding is that it is a privilege escalation bug within Kubernetes - and given that I work for a very small team where actually I’m the only one with access - I don’t think I’m immediately vulnerable. But my understanding is limited and I’m a fan of defence in depth so it’s time to upgrade.

Tangible Bytes

[related]
âŹ‡ïž
4,500 clusters still exposed to potential pre-auth RCE and working exploit available
👇
https://www.thestack.technology/the-one-with-ross-and-the-horrifying-kubernetes-vulnerability/

[PoC]
âŹ‡ïž
"Exploit for Ingress NGINX - IngressNightmare"
👇
https://github.com/hakaioffsec/IngressNightmare-PoC

#CyberVeille
#Kubernetes
#IngressNightmare
#CVE_2025_1974

The one with Ross and the critical Kubernetes vulnerability

4,500 clusters still exposed to potential pre-auth RCE and working exploit available

The Stack

⚠ Alerte sĂ©curitĂ© sur Kubernetes : #IngressNightmare

Le 24 mars 2025, l’équipe de recherche de Wiz et les mainteneurs de Kubernetes ont dĂ©voilĂ© 5 vulnĂ©rabilitĂ©s majeures affectant le trĂšs populaire Ingress-NGINX Controller (prĂ©sent sur +40% des clusters).

Ces failles, dont la plus grave est CVE-2025-1974 (CVSS 9.8), permettent Ă  un attaquant sans identifiants d’exĂ©cuter du code Ă  distance (Remote Code Execution) et de prendre le contrĂŽle complet du cluster Kubernetes, en accĂ©dant Ă  tous les secrets (mots de passe, clĂ©s d’API, etc.).

Ce qui est en cause :
Le composant vulnĂ©rable est le Validating Admission Controller d’Ingress-NGINX. Il valide les objets "Ingress" mais est, par dĂ©faut, accessible sans authentification depuis le rĂ©seau interne du cluster – parfois mĂȘme exposĂ© publiquement.

Les chercheurs ont rĂ©ussi Ă  injecter des configurations NGINX malveillantes, puis Ă  exĂ©cuter du code en important des bibliothĂšques Ă  partir de fichiers temporaires via NGINX. Une vĂ©ritable porte d’entrĂ©e invisible.

✅ Ce que vous devez faire rapidement:
Vérifiez si vous utilisez ingress-nginx :

kubectl get pods --all-namespaces --selector app.kubernetes.io/name=ingress-nginx

Mettez à jour vers une version corrigée :

v1.12.1 ou v1.11.5

Si vous ne pouvez pas mettre Ă  jour tout de suite :

DĂ©sactivez temporairement le webhook d’admission (voir instructions officielles).

[Sources officielles]
âŹ‡ïž
Blog de recherche Wiz :
"IngressNightmare: 9.8 Critical Unauthenticated Remote Code Execution Vulnerabilities in Ingress NGINX"
👇
https://www.wiz.io/blog/ingress-nginx-kubernetes-vulnerabilities

📱 Annonce de Kubernetes (Security Response Committee) :
"Ingress-nginx CVE-2025-1974: What You Need to Know"
👇
https://kubernetes.io/blog/2025/03/24/ingress-nginx-cve-2025-1974/

#CyberVeille #Kubernetes #DevSecOps #CVE_2025_1974 #RCE

Remote Code Execution Vulnerabilities in Ingress NGINX | Wiz Blog

Wiz Research uncovered RCE vulnerabilities (CVE-2025-1097, 1098, 24514, 1974) in Ingress NGINX for Kubernetes allowing cluster-wide secret access.

wiz.io