social.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
social.lol is a lighthearted social hangout for the omg.lol community.

Administered by:

Server stats:

834
active users

#devsecops

12 posts11 participants0 posts today

Regal v0.32.0 just dropped! After having worked mostly on language server features recently, it was time for the linter to get some love. This release includes 3 new linter rules as well as much faster linting. Check it out!

github.com/StyraInc/regal/rele

This release adds 3 new linter rules to Regal, as well as many improvements and fixes.
New Rule: redundant-loop-count
A loop iterating over empty collections evaluates to nothing, and counting the ...
GitHubRelease v0.32.0 · StyraInc/regalThis release adds 3 new linter rules to Regal, as well as many improvements and fixes. New Rule: redundant-loop-count A loop iterating over empty collections evaluates to nothing, and counting the ...
#OPA#Rego#Regal

⚠️ 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"
👇
wiz.io/blog/ingress-nginx-kube

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

wiz.io · Remote Code Execution Vulnerabilities in Ingress NGINX | Wiz BlogWiz Research uncovered RCE vulnerabilities (CVE-2025-1097, 1098, 24514, 1974) in Ingress NGINX for Kubernetes allowing cluster-wide secret access.

Wow, things are getting wild in the Kubernetes world! The name alone – "IngressNightmare" – gives me chills! 🤯 It's crucial to know this affects the Ingress NGINX Controller, *not* the NGINX Ingress Controller. That's a big difference!

Wiz really uncovered something huge. We're talking over 6,500 vulnerable clusters, with the potential for some serious Remote Code Execution (RCE). Ouch! They found that a scary 43% of cloud environments are impacted.

It appears, that these kinds of vulnerabilities often slip past standard scans. You really need manual penetration testing to catch them. And as a pentester myself, I can tell you, it's frequently like digging for buried treasure! 😅

Here are the CVEs to watch out for: CVE-2025-24513, CVE-2025-24514, CVE-2025-1097, CVE-2025-1098, CVE-2025-1974. These have a CVSS score of 9.8! So, you'll want to update to 1.12.1, 1.11.5, or 1.10.7 *immediately*. Another crucial step? See if your Admission Webhook Endpoint is exposed. Make sure you're limiting access. Don't need it? Then, turn it off!

So, what are your experiences with K8s security? I'm curious, what tools do you swear by? 🤔

OWASP Global AppSec EU 2025 Barcelona: full training schedule is out now!

Day 3 is packed with even more hands-on training sessions to enhance your AppSec expertise! Whether you're new to the field or looking to sharpen your skills, this day promises deeper dives into the latest security techniques and tools.

View the full agenda and register now:
owasp.glueup.com/event/owasp-g

Optimize Your AppSec Tools at OWASP Global AppSec 2025 EU in Barcelona!

2-Day Training | May 27-28, 2025
Level: Beginner | Trainer: Josh Grossman

Led by Josh Grossman, this updated course focuses on practical, vendor-neutral strategies to streamline workflows, automate processes, and measure your security improvements effectively without slowing down your CI/CD pipelines.

Register: owasp.glueup.com/event/123983/

⚠️ *Alerte Sécurité * dans l’action GitHub– tj-actions/changed-files

Une vulnérabilité a été **activement exploitée dans l’action GitHub tj-actions/changed-files, mettant en danger les pipelines CI/CD et exposant des secrets sensibles.

🔴 Impact : Vol de credentials et compromission potentielle des workflows.

📅 Période à risque : 12 mars 2025 (00:00 UTC) - 15 mars 2025 (12:00 UTC)

Dépôts affectés :

Dépôts publics 📢 → Les logs étant accessibles publiquement, les secrets doivent être considérés comme ** compromis.**

Action recommandé: Faites pivoter tous les secrets sans attendre.

Dépôts privés → Moins exposés, mais toujours à risque. Rotation des secrets recommandée dès que possible.

⚡ Recommandation :

Si votre projet a exécuté cette action pendant la période à risque, changez immédiatement tous les secrets.

🔗 Sources :

Wiz.io

StepSecurity

wiz.io · GitHub Action tj-actions/changed-files supply chain attack | Wiz BlogA supply chain attack on GitHub Action tj-actions/changed-files caused many repositories to leak their secrets.

As part of the @ActiveState team, I’m proud to share insights from our 2025 State of Vulnerability Management and Remediation Report. Did you know that over 50% of vulnerabilities are exploited within 7 days of discovery?

🕒 This report dives into how DevSecOps teams can reduce Mean Time to Resolution (MTTR) and strengthen application security.

If you’re looking to stay ahead of open-source risks, download the report today and learn how to better protect your software supply chain! Read the press release here: prnewswire.com/news-releases/a

Download the report today: activestate.com/resources/whit