Mashable has reported the following regarding the Heartbleed bug: An encryption flaw called the Heartbleed bug is already being called one of the biggest security threats the Internet has ever seen.

The bug has affected many popular websites and services — ones you might use every day, like Gmail and Facebook — and could have quietly exposed your sensitive account information (such as passwords and credit card numbers) over the past two years. But it hasn’t always been clear which sites have been affected.

Mashable reached out some of the most popular social, email, banking and commerce sites on the web. We’ve rounded up their responses below. Some Internet companies that were vulnerable to the bug have already updated their servers with a security patch to fix the issue. This means you’ll need to go in and change your passwords immediately for these sites. Even that is no guarantee that your information wasn’t already compromised, but there’s also no indication that hackers knew about the exploit before this week.

The companies that are advising customers to change their passwords are doing so as a precautionary measure. Although changing your password regularly is always good practice, if a site or service hasn’t yet patched the problem, your information will still be vulnerable. Also, if you reused the same password on multiple sites, and one of those sites was vulnerable, you’ll need to change the password everywhere. It’s not a good idea to use the same password across multiple sites, anyway.

Networks that were affected with statements from each:

Facebook “We added protections for Facebook’s implementation of OpenSSL before this issue was publicly disclosed. We haven’t detected any signs of suspicious account activity, but we encourage people to … set up a unique password.”

Instagram “Our security teams worked quickly on a fix and we have no evidence of any accounts being harmed. But because this event impacted many services across the web, we recommend you update your password on Instagram and other sites, particularly if you use the same password on multiple sites.”

Pinterest “We fixed the issue on Pinterest.com, and didn’t find any evidence of mischief. To be extra careful, we e-mailed Pinners who may have been impacted, and encouraged them to change their passwords.”

Tumblr “We have no evidence of any breach and, like most networks, our team took immediate action to fix the issue.”

Twitter Twitter wrote that OpenSSL “is widely used across the internet and at Twitter. We were able to determine that [our] servers were not affected by this vulnerability. We are continuing to monitor the situation.” While reiterating that they were unaffected, Twitter told Mashable that they did apply a patch.

Google “We have assessed the SSL vulnerability and applied patches to key Google services.” Search, Gmail, YouTube, Wallet, Play, Apps and App Engine were affected; Google Chrome and Chrome OS were not. *Google said users do not need to change their passwords, but because of the previous vulnerability, better safe than sorry.

Yahoo “As soon as we became aware of the issue, we began working to fix it… and we are working to implement the fix across the rest of our sites right now.” Yahoo Homepage, Yahoo Search, Yahoo Mail, Yahoo Finance, Yahoo Sports, Yahoo Food, Yahoo Tech, Flickr and Tumblr were patched. More patches to come, Yahoo says.

Gmail “We have assessed the SSL vulnerability and applied patches to key Google services.” *Google said users do not need to change their passwords, but because of the previous vulnerability, better safe than sorry.

Yahoo Mail “As soon as we became aware of the issue, we began working to fix it… and we are working to implement the fix across the rest of our sites right now.”

Amazon Web Services (for website operators) Most services were unaffected or Amazon was already able to apply mitigations (see advisory note here). Elastic Load Balancing, Amazon EC2, Amazon Linux AMI, Red Hat Enterprise Linux, Ubuntu, AWS OpsWorks, AWS Elastic Beanstalk and Amazon CloudFront were patched.

Etsy Etsy said that only a small part of its infrastructure was vulnerable, and they have patched it.

GoDaddy “We’ve been updating GoDaddy services that use the affected OpenSSL version.”

USAA USAA said that it has “already taken measures to help prevent a data breach and implemented a patch earlier this week.”

Box “We’re currently working with our customers to proactively reset passwords and are also reissuing new SSL certificates for added protection.”

Dropbox On Twitter: “We’ve patched all of our user-facing services & will continue to work to make sure your stuff is always safe.”

GitHub GitHub said it has patched all its systems, deployed new SSL certificates and revoked old ones. GitHub is asking all users to change password, enable two-factor authentication and “revoke and recreate personal access and application tokens.”

IFTTT IFTTT emailed all its users and logged them out, prompting them to change their password on the site.

Minecraft “We were forced to temporary suspend all of our services. … The exploit has been fixed. We can not guarantee that your information wasn’t compromised.” More Information

Netflix “Like many companies, we took immediate action to assess the vulnerability and address it. We are not aware of any customer impact.”

OKCupid “We, like most of the Internet, were stunned that such a serious bug has existed for so long and was so widespread.”

SoundCloud SoundCloud emphasized that there were no indications of any foul play and that the company’s actions were simply precautionary.

SpiderOak Spideroak said it patched its servers, but the desktop client doesn’t use a vulnerable version of OpenSSL, so “customers do not need to take any special action.”

WordPress WordPress tweeted that it has taken “immediate steps” and “addressed the Heartbleed OpenSSL exploit,” but it’s unclear if the issue is completely solder. When someone asked Matt Mullenweg, WordPress’ founding developer, when the site’s SSL certificates will be replaced and when users will be able to reset passwords, he simply answered: “soon.”

Wunderlist “You’ll have to simply log back into Wunderlist. We also strongly recommend that you reset your password for Wunderlist.” Full Statement

Dashlane Dashlane said in a blog post users’ accounts were not impacted and the master password is safe as it is never transmitted. The site does use OpenSSL when syncing data with its servers but Dashlane said it has patched the bug, issued new SSL certificates and revoked previous ones.

LastPass “Though LastPass employs OpenSSL, we have multiple layers of encryption to protect our users and never have access to those encryption keys.” Users don’t need to change their master passwords because they’re never sent to the server. But passwords for other sites stored in LastPass might need to be changed. The following have NOT been affected by this  and were not running the OpenSSL software:

  • LinkedIn
  • Apple
  • PayPal
  • Ebay
  • Microsoft
  • AOL
  • HotMail/Outlook
  • Amazon
  • Groupon
  • Target
  • Walmart
  • Evernote
  • Nordstrom

Reporters who contributed to this story include Samantha Murphy Kelly, Lorenzo Francheschi-Bicchierai, Seth Fiegerman, Adario Strange and Kurt Wagner.

Facebooktwitterredditpinterestlinkedinmail