Leaked information can include usernames, passwords and personal messages, OAuth tokens. Worse, some of them are also indexed by search engines (Cloudflare says about 700 pages). ) means that if you search on Google, you will see sensitive information when users log in.
This error was not detected in about 5 months and was patched immediately after being detected. Cloudflare said 'the most affected period is February 13 to February 18 with about 1 out of 3.3 million HTTP requests via Cloudflare likely to leak. (equivalent to 0.00003%).
The number is small but with a popular service like Cloudflare, this is a significant number. Some people also list the list of Cloudflare sites with more than 4 million domain names, including Uber, Medium . (some mobile applications are also affected).
If you are a programmer or have knowledge of programming, you can read about this error at Cloudflare's blog page. Posts about Cloudbleed on Cloudflare's blog https://blog.cloudflare.com/incident-report-on-memory-leak-caused-by-cloudflare-parser-bug/
If you are using Cloudflare, you may also be interested in the newly released DNS 1.1.1.1 service, which not only increases security but also brings faster connection speeds.
See more: