An improper file permissions vulnerability affects Kata Containers prior to 1.11.5. When using a Kubernetes hostPath volume and mounting either a file or directory into a container as readonly, the file/directory is mounted as readOnly inside the container, but is still writable inside the guest. For a container breakout situation, a malicious guest can potentially modify or delete files/directories expected to be read-only.
Related Articles
All Mix →Analyzing Threat Reports with Fabric
We’ve just added a new Pattern to fabric. It’s called analyze_threat_report, and it’s designed to extract all the most valuable parts of a cybersecurity threat…
Awards to Detectify’s team members
Table of Contents Super talents of 2015 Security experts of the future International Startup Award We’re looking for more talents! Team members of Detectify have…
[tl;dr sec] #296 – AI Automates CVE -> Exploit, Apple Defeats Memory Corruption, Moar NPM Backdoors
Table of Contents AI auto-generating exploits from CVEs for $3, not actually but Memory Integrity Enforcement makes it harder, surprisingly NPM packages were backdoored Bardcore…
[tl;dr sec] #211 – LLMs + Fuzzing, Navigating the Incident Response Maze, Product Security @ HashiCorp
Table of Contents 🎅 Last tl;dr sec until January 4th AppSec Cloud Security Container Security Blue Team Red Team Machine Learning + Security Misc ✉️…
🎙️ Hacking, Open Source and Bug Bounty (Live Podcast) #3
🎙️ Hacking, Open Source and Bug Bounty (Live Podcast) #3 Source link
How Detectify handles Zero-Day submissions
Table of Contents What is a 0-day? Does Detectify scan for 0-days? How Detectify handles 0-days reports When are 0-days disclosed by Detectify? 0-days…

