Default seccomp profiles turn container breakout risk into a narrower syscall surface
Kubernetes seccomp defaults, privileged exceptions, and runtime verification.
Tag archive
Kubernetes seccomp defaults, privileged exceptions, and runtime verification.
Container and VM control planes are privileges in themselves. The exposure counts are small and the consequence of a badly exposed one is not.
How user namespace mapping changes what container root means, and why the setting needs an explicit decision.
ZoomEye observed 177 hosts answering on port 2375, the unencrypted Docker API. Why a small exposure count can carry more risk than a large one.
How admission control is ordered, what built-in Pod Security covers, and what a parameterised policy engine adds for enforcement and audit.
6,378,556 listening services on port 10250 and the short path from an exposed cluster node interface to workload credentials.
A pair of critical PHP engine flaws and eight eMudhra intermediate certificates with computable private keys landed in the same week, and for container users both are fixed the same way: rebuild on a patched base, then redeploy. An image carries its own trust store, so it keeps trusting bad certificates until someone rebuilds it.
174 reachable Docker daemons on port 2375, and why a small exposure count can outrank a large one.
174 Unauthenticated Docker Daemons: Why a Small Number Is Still Worth Acting On A ZoomEye...
ZoomEye finds 298,430 endpoints matching the unauthenticated Docker API on port 2375. Why this exposure is directly exploitable and how to close it.

One wrong package name can run attacker code on your laptop or CI Honestly, I'd say npm...
AppArmor and seccomp Profiles: Restricting Container System Calls A Senior...