So they have no idea what caused this file to double in size and propagate itself across the network. And their fix was just to replace it with an older version.
There doesn't appear to be anything preventing this problem from happening again.
this post was submitted on 19 Nov 2025
22 points (100.0% liked)
Pulse of Truth
1722 readers
207 users here now
Cyber Security news and links to cyber security stories that could make you go hmmm. The content is exactly as it is consumed through RSS feeds and wont be edited (except for the occasional encoding errors).
This community is automagically fed by an instance of Dittybopper.
founded 2 years ago
MODERATORS
Prince explained that the problem “was triggered by a change to one of our database systems’ permissions which caused the database to output multiple entries into a ‘feature file’ used by our Bot Management system.
They know what caused the file size increase, exactly what system it broke and how.
Cloudflare will work on “hardening ingestion of Cloudflare-generated configuration files in the same way we would for user-generated input; enabling more global kill switches for features; eliminating the ability for core dumps or other error reports to overwhelm system resources; [and] reviewing failure modes for error conditions across all core proxy modules,” according to Prince.
And they’re planning to prevent future occurrences.
Seriously did you not read the article?