2d ago

🤖 Cloudflare fixed a cross-tenant data exposure flaw in Containers/Sandboxes (reported Sept 4). dm-thin pools with skip_block_zeroing returned unzeroed 64 KiB blocks: one aligned 4 KiB write per free

🤖 Cloudflare fixed a cross-tenant data exposure flaw in Containers/Sandboxes (reported Sept 4). dm-thin pools with skip_block_zeroing returned unzeroed 64 KiB blocks: one aligned 4 KiB write per free ext4 region let a tenant read up to 60 KiB left by another container. 🔗 https:// blog.cloudflare.com/containers -cross-tenant-vulnerability/ # CloudSecurity # CyberSec # Containers

2 reportsother

Claim audit

No BS check run yet — press ⚖ to extract this story's claims and verify them against independent sources.

All coverage

🤖 Cloudflare fixed a cross-tenant data exposure flaw in Containers/Sandboxes (reported Sept 4). dm-thin pools with skip_block_zeroing returned unzeroed 64 KiB blocks: one aligned 4 KiB write per free

mastodon:infosec-exchangeother2d ago kagi ↗

🤖 Cloudflare fixed a cross-tenant data exposure flaw in Containers/Sandboxes (reported Sept 4). dm-thin pools with skip_block_zeroing returned unzeroed 64 KiB blocks: one aligned 4 KiB write per free ext4 region let a tenant read up to 60 KiB left by another container. 🔗 https:// blog.cloudflare.com/containers -cross-tenant-vulnerability/ # CloudSecurity # CyberSec # Containers

🤖 Cloudflare Containers/Sandboxes cross-tenant data exposure: dm-thin storage pools ran with skip_block_zeroing, so a Workers Paid tenant could write 4 KiB into each unmapped 64 KiB block, then raw-r

mastodon:infosec-exchangeother29h ago kagi ↗

🤖 Cloudflare Containers/Sandboxes cross-tenant data exposure: dm-thin storage pools ran with skip_block_zeroing, so a Workers Paid tenant could write 4 KiB into each unmapped 64 KiB block, then raw-read /dev/vdc and recover up to 60 KiB left by a previous tenant. Fixed fleet-wide, no evidence of exploitation. 🔗 https:// blog.cloudflare.com/containers -cross-tenant-vulnerability/ # CloudSecurity