Your sensitive data may have been leaked from one of several big-name websites that were potentially affected by a typo in the code of hosting provider Cloudflare.
Private encryption keys, cookies, passwords, and HTTPS requests have all been spotted in public caches following a colossal error that let random bits of server memory slip into webpages during certain processes.
Most people aren’t familiar with Cloudflare, but have heard of at least a few of the millions of companies whose details may have leaked, including Uber, Fitbit, Yelp, 4chan, and OK Cupid.
Site is temporarily down due to a @CloudFlare network issue: https://t.co/0h2q5Q9TNx
— 4chan (@4chan) October 2, 2014
Tavis Ormandy, a security researcher at Google, first spotted the breach and immediately let Cloudflare know about it. The company fixed the problem just two days later, but the damage was done. Cloudflare learned the earliest leak dates all the way back to September 2016, which means personal information has been “randomly” appearing on websites for months.
Ormandy found hotel bookings, passwords, and messages from dating sites among the cached data. “I didn’t realize how much of the internet was sitting behind a Cloudflare CDN until this incident,” he wrote. “We’re talking full https requests, client IP addresses, full responses, cookies, passwords, keys, data, everything.”
That info was found stored in web browser cached pages. With help from Google, Yahoo, Bing, and others, 770 unique resource identifiers (URIs) were found that had been cached and contained leaked memory. Of those, 161 came from unique websites, according to a lengthy post Cloudflare wrote about the incident.
The root cause for the issue comes from the company’s use of a new HTML parser, which is basically a search bar for code that lets you easily find and edit sections of information. It underwent a buffer overflow, which Cloudflare says could have been avoided if it had simply been checked with “>=” instead of “==.”
Basically, a tiny error caused a massive problem.
The company says the greatest period of impact was from Feb. 13-18, with around one in every 3,300,000 HTTP requests through Cloudflare potentially resulting in memory leakage (around 0.00003% of requests). That may not seem like a lot, until you consider millions of businesses—including some of the world’s largest—use the service.
In a blog post, security expert Ryan Lackey offered some advice to everyone who uses the internet: Change your password and use two-factor verification.
“Cloudflare is behind many of the largest consumer web services (Uber, Fitbit, OKCupid, …), so rather than trying to identify which services are on Cloudflare, it’s probably most prudent to use this as an opportunity to rotate ALL passwords on all of your sites,” Lackey wrote. “Users should also log out and log in to their mobile applications after this update. While you’re at it, if it’s possible to use 2FA or 2SV with sites you consider important.”
Cloudflare claims to have not yet identified any malicious uses of the information.
This massive leak is just the latest in an endless string of incidents that make you want to hate the internet. The advice coming out of all of them is to continue to rotate your passwords, or simply use two-step or two-factor verification for all of your accounts.
A list of websites potentially affected by Cloudflare’s leak is being compiled on Github.
H/T the Verge
