I didn't even think about this yet, but linting file- and directory names in project structures makes a lot of sense - and there is of course a tool for it:
Infosec Enthusiast & Practitioner. Opinions are my own. Pentest→Research→Leading→Security Engineering. Love Martial Arts, Outdoors, Dogs.
I didn't even think about this yet, but linting file- and directory names in project structures makes a lot of sense - and there is of course a tool for it:
Alright AKS, pick a lane:
Kubenet: Pods receive IP from an overlay network. Retires March 2028
Azure CNI Standard: Pods receive IP from VNET
Azure CNI Overlay: Pods receive IP from an overlay network.
Great article on using GitHub as a workflow platform:
https://github.blog/engineering/issueops-automate-ci-cd-and-more-with-github-issues-and-actions/
Can absolutely recommend for security workflows and management as well!
Quite some #IngressNightmare #CVE-2025-1974 PoCs on GitHub now that look good at a cursory review:
https://github.com/hakaioffsec/IngressNightmare-PoC
https://github.com/yoshino-s/CVE-2025-1974/
https://github.com/Esonhugh/ingressNightmare-CVE-2025-1974-exps/
https://github.com/hi-unc1e/CVE-2025-1974-poc/
https://github.com/lufeirider/IngressNightmare-PoC
https://github.com/zwxxb/CVE-2025-1974
https://github.com/rjhaikal/POC-IngressNightmare-CVE-2025-1974
Quick note on exploits trying to use `nginx.ingress.kubernetes.io/server-snippet`: That annotation has been identified as an issue before and has been disabled to mitigate CVE-2021-25742.
@raesene True, quite some good stuff out now!
@raesene Hm, the ones I looked at were quite lacking :D But that was two days ago and reliable exploit did not take that long. Will have a look, thx :)
I wrote up some details on exploiting #IngressNightmare #CVE-2025-1974:
www.averlon.ai/blog/kuberne...
Where are we at with releasing a full PoC?
Wow, GitHub not supporting IPv6 for Webhooks:
https://docs.github.com/en/webhooks/about-webhooks#about-webhooks-on-github
in switzerland you aren't allowed to have a train with exactly 256 axles because of an integer overflow in the axle counting machine
i wish i could fix my software bugs by making it illegal to cause them
One long plane ride later and my cloud security knowledge base is finally transformed into a proper awesome-repo:
https://github.com/uchi-mata/awesome-cloud-security
There are lots of good cloud security knowledge collections out there, but maybe this is helpful for some 🙂
Could be a very interesting metric when trying to triage vulnerabilities 🙃
If you need some more interactivity while wrangling those jq queries:
Collection of known-malicious packages/package identifiers:
Nobody:
Azure Chief Naming Officer: Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux)
Continuing the discussion on CVE data: here’s one for thought as we head into the weekend — CVE-2022-26520.
- Vulnerability requires an attacker to be able to modify application code around the postgres database connector.
- According to CVSS ratings, it’s categorized as low complexity, requiring no user interaction or prior privileges.
While there might be situations in which those ratings ratings are technically accurate, they don’t fully reflect the practical realities of exploiting this vulnerability.
Another perfect example of the challenges in our CVE data/ecosystem:
https://gitlab.freedesktop.org/cairo/cairo/-/issues/341
- Bug is difficult to reproduce, not clear whether it is exploitable anywhere at all
- Bug was reported/discussed 6 years ago
- CVE created 4 years ago
- 3 years ago someone asks whether this was fixed
- No activity since
- CVE: Exists and gets reported by scanners.
Kubernetes has a great debugging feature that lets you to start ephemeral containers in an existing pod:
https://lnkd.in/eaqES9cU
This feature enables you to keep your production containers minimal (read: with minimal attack surface and patching effort) while still retaining debugging capabilities. However, not all container runtimes supported this in the past.
Good news: for over a year now, all major container runtimes have supported this feature (at least, the last time I checked!).
I have little insight into the commercial legacy firewall vendors these days anymore, but I always wanted DNS-based policies 6+ years back when I still occasionally had to deal with them. So seeing Calico's domain-based network policies is ✨ ✨✨ for me (in a standardized text-based machine-processable format even).
Hi all, I'm looking for a new team member to join the infosec team @camunda . The role is a GRC analyst role that will focus on audits and compliance monitoring. We are a pretty technical team where automation has a strong focus. If that sounds interesting to you check out the link(salary ranges based on location included inside): https://camunda.com/jobs/?gh_jid=6240088003
My favorite scene with Maggie Smith...