Security Alerts & News
by Tymoteusz A. Góral

History
#2036 List of sites possibly affected by Cloudflare's Cloudbleed HTTPS traffic leak
Between 2016-09-22 - 2017-02-18 session tokens, passwords, private messages, API keys, and other sensitive data were leaked by Cloudflare to random requesters. Data was cached by search engines, and may have been collected by random adversaries over the past few months.

Requests to sites with the HTML rewrite features enabled triggered a pointer math bug. Once the bug was triggered the response would include data from ANY other Cloudflare proxy customer that happened to be in memory at the time. Meaning a request for a page with one of those features could include data from Uber or one of the many other customers that didn't use those features. So the potential impact is every single one of the sites using Cloudflare's proxy services (including HTTP & HTTPS proxy).

"The greatest period of impact was from February 13 and February 18 with around 1 in every 3,300,000 HTTP requests through Cloudflare potentially resulting in memory leakage (that’s about 0.00003% of requests), potential of 100k-200k paged with private data leaked every day"
Read more
#2041 Security lapse exposed New York airport's critical servers for a year
#2040 Watershed SHA1 collision just broke the WebKit repository, others may follow
#2039 Linus Torvalds on SHA1 and Git: 'The sky isn't falling'
#2038 SHA1 collider
#2037 Removing user admin rights mitigates 94% of all critical Microsoft vulnerabilities
#2036 List of sites possibly affected by Cloudflare's Cloudbleed HTTPS traffic leak
#2035 How security products are tested – part 1
#2034 The real cost of ransomware: Attacks take most victims offline for at least a week
History
2017: 01 02 03 04 05
2016: 01 02 03 04 05 06 07 08 09 10 11 12