Live data from Hacker News

Cloudflare Reverse Proxies Are Dumping Uninitialized Memory

bugs.chromium.org

171–180 of 1001 posts

Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory

#171

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.

True, but I'd hope that NDEBUG is now widely recognized as being a horrible misfeature.

Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory

#172
post #39

Earlier 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

I don't think that's the case: from my reading of the issue I understood that the urls with query params were sent from CF to Google for clearing from the google cache.

Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory

#173

Earlier 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 ?

$ host -t NS digitalocean.com

digitalocean.com name server walt.ns.cloudflare.com.

digitalocean.com name server kim.ns.cloudflare.com.

Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory

#174

Earlier 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 ?

[deleted]

Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory

#176

Earlier 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)?

Not just headers, basically random memory dumps that could contain anything that Cloudflare saw (which is almost everything). Passwords, certificates, you name it.

Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory

#177

Cloudflare 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…

You are essentially arguing against freedom of speech. Cloudflare will protect any site that doesn't host child porn. Yes that includes things which you don't like, but it also includes all the things you do.

Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory

#178
post #58

Earlier 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.

Because you'll make much more working for people who specifically hire you instead of doing a bunch of risky work on spec.

Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory

#179
post #123

Earlier 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.

If Cloudflare accidentally leaked additional sensitive data to Tavis during the handling of this incident, and that data wasn't already compromised by the parser bug, then you should call that out in the incident report.

Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory

#180
post #106

So how does one find or generate a list of companies using CloudFlare to figure out how you're affected - kinda like HaveIBeenPwned.com?

it doesn't seem to matter since _ANY_ service that CF gave data to could possibly have cached it and thus have a random site's secrets.
Post reply on HN