CRITICAL: Deployed containers have no security constraints (capabilities, seccomp, resource limits) #110
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Containers created by upaas have zero security hardening. User-provided Dockerfiles run with full default Docker capabilities, no seccomp profile, no AppArmor, no resource limits, and
RestartPolicyUnlessStopped.Location
internal/docker/client.go—CreateContainer()method (line ~185)Impact
This is a PaaS platform — users deploy arbitrary code. Without constraints:
CAP_SYS_ADMINpotential via user namespaces,CAP_NET_RAWfor network attacksCAP_NET_RAWallows ARP spoofing, packet sniffing on the Docker networkCurrent Code
Suggested Fix
Add to
HostConfig:Make limits configurable per-app (add columns to apps table for memory_limit, cpu_limit).
Severity
CRITICAL — Without this, any deployed app can DoS the host or attempt container escape.
WONTFIX, working as intended