Update from Cloudflare on Cloudbleed

soccer97

Level 11
Thread author
Verified
Forum Veteran
May 22, 2014
516
766
967
Updated information from Cloudflare regarding Cloudbleed:

On February 23, 2017, Cloudflare CTO John Graham-Cumming published a blog post describing a memory leak caused by a serious bug that impacted Cloudflare's systems. Please read the blog post here for full details:

Incident report on memory leak caused by Cloudflare parser bug

While we fully resolved the bug within hours of it being reported to us, there was an ongoing risk that some of our customers' sensitive information would still be available through third party caches, such as the Google search cache.

Over the last week, we've worked with these caches to discover what customers may have had sensitive information exposed and ensure that the caches are purged. We waited to disclose the bug publicly until after these caches could be cleared in order to mitigate the potential impact and ability of malicious individuals to exploit any leaked data.

This was updated yesterday morning. There is a recommendation for site owners.