Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
bugs.chromium.org
Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
1–10 of 1001 posts
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#2Full details from Cloudflare: https://blog.cloudflare.com/incident-report-on-memory-leak-c...
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#3Full details from Cloudflare: https://blog.cloudflare.com/incident-report-on-memory-leak-c...
... and the HN link/discussion (submitted by jgrahamc): https://news.ycombinator.com/item?id=13718720
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#4Oh, my god.
Read the whole event log.
If you were behind Cloudflare and it was proxying sensitive data (the contents of HTTP POSTs, &c), they've potentially been spraying it into caches all across the Internet; it was so bad that Tavis found it by accident just looking through Google search results.
The crazy thing here is that the Project Zero people were joking last night about a disclosure that was going to keep everyone at work late today. And, this morning, Google announced the SHA-1 collision, which everyone (including the insiders who leaked that the SHA-1 collision was coming) thought was the big announcement.
Nope. A SHA-1 collision, it turns out, is the minor security news of the day.
This is approximately as bad as it ever gets. A significant number of companies probably need to compose customer notifications; it's, at this point, very difficult to rule out unauthorized disclosure of anything that traversed Cloudflare.
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#5>Cloudflare pointed out their bug bounty program, but I noticed it has a top-tier reward of a t-shirt.
Considering the amount and sensitivity of the data they handle, I'm not sure a t-shirt is an appropriate top-tier reward.
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#6Oh, my god. Read the whole event log. If you were behind Cloudflare and it was proxying sensitive data (the contents of HTTP POSTs, &c), they've potentially been spraying it into caches all across the Internet; it was so bad that Tavis found it by accident just looking through Google search results. The crazy thing here is that the Project Zero people were joking last night about a disclosure that was going to keep e…
[deleted]
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#7Wow apparently they never fuzzed their input and looked at the output. A malformed html input should be about the easiest possible thing to try... yeouch...
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#8Well, my day tomorrow is going to be busy. So's my evening tonight, I guess.
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#9Oh, my god. Read the whole event log. If you were behind Cloudflare and it was proxying sensitive data (the contents of HTTP POSTs, &c), they've potentially been spraying it into caches all across the Internet; it was so bad that Tavis found it by accident just looking through Google search results. The crazy thing here is that the Project Zero people were joking last night about a disclosure that was going to keep e…
I remember Tavis tweeted Friday night asking for a cloudflare engineer to contact him, and everyone joked that the last thing you want on a Friday evening is an urgent message from tavis ormandy.
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#10Neither this thread nor the Cloudflare blog post include concise steps for customers who were exposed.
There's an argument for changing secrets (user passwords, API keys, etc.) for potentially affected sites, plus of course investigating logs for any anomalous activity. It would be nice if there were a guide for affected users, maybe a supplemental blog post.
(and yet again: thank you Google for Project Zero!)