Cloudflare fixes Containers flaw that could have exposed other customers' data

· CyberSecurity

TLDR

  • Cloudflare fixed a Containers bug that could have let a Workers Paid customer read leftover data from other tenants' containers.1
  • A shared storage pool skipped zeroing reused 64 KiB blocks, breaking the isolation multi-tenant platforms rely on.1
  • Cloudflare says it found no evidence any customer data was exposed in production.1

A researcher found that Cloudflare's Containers service, which runs containerised apps on the Workers Paid plan, stored container disks in a shared pool that did not zero out reused 64 KiB storage blocks after a container was deleted.1 By writing just 4 KiB of data into an unused region of a new container's disk, an attacker could trigger allocation of one of these reused blocks and read the remaining 60 KiB of a previous tenant's leftover data, which could include directory structures, database pages, and complete SQLite databases.1

Oren Yomtov, a researcher at Accomplish, reported the flaw through HackerOne on 4 September.1 Testing across 24 container placements on 22 underlying nodes found residual material in 18 of the placements and on 20 of the nodes, including .env files and Chromium browser profiles, though the researchers only counted matches rather than extracting live data, and attackers had no control over whose container they landed next to and could not read an actively attached disk.1 Cloudflare said it reviewed its logs, telemetry, and historical data and found no evidence that any customer's data was exposed through this method in production, and completed remediation, including removing the setting that skipped block zeroing and retiring existing container disks, by 19 September.1 In its own writeup, Cloudflare said the affected pools used a 64 KiB thin block size under Linux's dm-thin provisioning with the skip_block_zeroing option set, so a full-block write replaced a reused block's contents but a smaller write left the remainder recoverable, and that within its historical disk I/O telemetry the only activity it could attribute to the technique came from the researchers and Cloudflare engineers conducting authorised validation.2

Why it matters: the flaw shows that a routine storage optimisation, skipping a zeroing step to save time, can silently break the isolation multi-tenant cloud platforms depend on, so even though Cloudflare found no evidence of real-world exposure here, similar shared-storage shortcuts elsewhere could be leaking one customer's files to another right now.

Sources

  1. Cloudflare fixes Containers cross-tenant flaw exposing customer data (BleepingComputer)
  2. How Cloudflare addressed a cross-tenant data exposure vulnerability in Containers (Cloudflare)