Earlier quoted context omitted.
Even a >= check would have been suboptimal. Rather than /* generated code */ if ( ++p == pe ) goto _test_eof; or /* generated code */ if ( ++p >= pe ) goto _test_eof; they should have had /* generated code */ if ( ++p == pe ) goto _test_eof; assert(p since having servers core dumping would have drawn attention to the bug in a way that counting one byte too many and then hitting _test_eof would not.
Some assert() macros are disabled on release builds, so that's not exactly safe either.
Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
171–180 of 1001 posts
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#172Earlier quoted context omitted.
The quoted part that specifically mentions logged urls containing query strings has nothing to do with logging?
That's Google logging stuff
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#173Earlier quoted context omitted.
> My second thought after relief was the realization that even as a consumer I'm affected by this, my password manager has > 100 entries what percentage of them are using CloudFlare? Should I change all my passwords? Yes. Right now. Don't wait for the vendor to notify you. > What an epic mess. This is the problem with centralization, the system is broken. Yep.
How do you check if a website uses cloudflare ? Any scripts that do that ?
digitalocean.com name server walt.ns.cloudflare.com.
digitalocean.com name server kim.ns.cloudflare.com.
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#174Earlier quoted context omitted.
> My second thought after relief was the realization that even as a consumer I'm affected by this, my password manager has > 100 entries what percentage of them are using CloudFlare? Should I change all my passwords? Yes. Right now. Don't wait for the vendor to notify you. > What an epic mess. This is the problem with centralization, the system is broken. Yep.
How do you check if a website uses cloudflare ? Any scripts that do that ?
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#175Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#176Earlier quoted context omitted.
Headers (among other sensitive stuff) were being leaked inside document bodies.
So just to clarify: some bug makes Cloudflare leak the HTTP Headers into the HTML being served and those HTML pages containing sensitive Info got cached by Google (and others)?
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#177Cloudflare isn't just a security hole in the middle of the internet, they're a protection racket. If you wanted to pay to DDoS a site, search for "booter" and you'll get a list of sites that will take another site off the internet for money with a flood of traffic. quezstresser.com webstresser.co topbooter.co instabooter.com booter.xyz critical-boot.com top10booters.com betabooter.com databooter.com etc. etc. - from…
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#178Earlier quoted context omitted.
If serious researchers are looking to get paid, I think bug bounties are the wrong approach entirely
Why? Many can help find problems without having to be full-time, that's the point of crowd-sourcing with payouts.
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#179Earlier quoted context omitted.
That's not how Google tells it, if I'm reading this right: Cloudflare explained that they pushed a change to production that logged malformed pages that were requested, and then sent me the list of URLs to double check. Many of the logged urls contained query strings from https requests that I don't think they intended to share. (I'm reading that as "intended to share with Google".)
Ah. I see what you mean. Apologies, kind of tired.
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#180So how does one find or generate a list of companies using CloudFlare to figure out how you're affected - kinda like HaveIBeenPwned.com?