Cloudflare Fixes Cross-Tenant Data Exposure in Containers
A storage-allocation setting—not the Firecracker VM boundary—allowed some Cloudflare Containers customers to read residual bytes from other tenants’ disks. Cloudflare says it fixed the issue and found no evidence of malicious exploitation.
With dm-thin’s 64 KiB blocks and skip_block_zeroing enabled, a 4 KiB write could allocate a block while leaving up to 60 KiB of prior contents untouched. Researchers recovered directory metadata, database pages, and complete SQLite databases across multiple placements. Exposure was opportunistic: an attacker could not select a victim or host, and the report found no cross-tenant writes or availability impact. Cloudflare disabled the setting, then drained hosts and retired existing disks and image caches so already-mapped blocks would be cleared too.
The article links practitioner reactions stressing that tenant isolation must include storage reuse and zeroing—not just the VM boundary. InfoQ has no reader-comment section.