CloudFlare parser bug incident and Gamers With Jobs

You all may be hearing today about a CloudFlare security incident that occurred during the month of February 2017. Gamers With Jobs utilizes CloudFlare for D/DoS protection as well as static asset caching. So, I wanted to let you all know that I've followed the issues and received word from CloudFlare that gamerswithjobs.com was not impacted by this incident. I've copied the full email I received from CloudFlare below.

In response to the incident, I have cleared all active Drupal sessions, forcing all users to re-authenticate (log back in). With regard to the incident in general, CloudFlare handles traffic for many domains. In fact, it's amazing the issue only impacted 161 unique domains. Regardless, I recommend you pay attention to any emails you receive from other web services you utilize. They should contact you if they are aware their service was impacted by this issue.

CloudFlare wrote:

Dear Jeff,

Thursday afternoon, we published a blog post describing a memory leak caused by a serious bug that impacted Cloudflare's systems. If you haven't yet, I encourage you to read that post on the bug:

https://blog.cloudflare.com/incident...

While we resolved the bug within hours of it being reported to us, there was an ongoing risk that some of our customers' sensitive information would still be available through third party caches, such as the Google search cache.

Over the last week, we've worked with these caches to discover what customers may have had sensitive information exposed and ensure that the caches are purged. We waited to disclose the bug publicly until after these caches could be cleared in order to mitigate the ability of malicious individuals to exploit any exposed data.

In our review of these third party caches, we discovered exposed data on approximately 150 of Cloudflare's customers across our Free, Pro, Business, and Enterprise plans. We have reached out to these customers directly to provide them with a copy of the data that was exposed, help them understand its impact, and help them mitigate that impact.

Your domain is not one of the domains where we have discovered exposed data in any third party caches. The bug has been patched so it is no longer leaking data. However, we continue to work with these caches to review their records and help them purge any exposed data we find. If we discover any data leaked about your domains during this search, we will reach out to you directly and provide you full details of what we have found.

To date, we have yet to find any instance of the bug being exploited, but we recommend if you are concerned that you invalidate and reissue any persistent secrets, such as long lived session identifiers, tokens or keys. Due to the nature of the bug, customer SSL keys were not exposed and do not need to be rotated.

Again, if we discover new information that impacts you, we will reach out to you directly. In the meantime, if you have any questions or concerns, please don’t hesitate to reach out.

Matthew Prince
Cloudflare, Inc.
Co-founder and CEO

I presume that a change of password might be a good idea, just in case?