Ayer les presentamos todo acerca de Heartbleed, este fallo de seguridad del protocolo OpenSSL utilizado por más del 66% de páginas web y que puede haber comprometido tu información. Es por eso que ahora te traemos una lista de los servicios y páginas afectadas donde deberías cambiar de contraseña para prevenir cualquier robo de información.
| ¿Fué afectado? | ¿Ha parchado su sistema? | ¿Necesitas cambiar de contraseña? | ¿Qué ha dicho la compañía acerca del problema? | |
|---|---|---|---|---|
| No queda claro | Si | Si | «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.» | |
| Si | Si | Si | «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.” | |
| No | No | No | «We didn’t use the offending implementation of OpenSSL in www.linkedin.com or www.slideshare.net. As a result, HeartBleed does not present a risk to these web properties.» | |
| Si | Si | Si | «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 | Si | Si | Si | «We have no evidence of any breach and, like most networks, our team took immediate action to fix the issue.» |
| No | Si | No queda claro | 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 toldMashable that they did apply a patch. |
| ¿Fué afectado? | ¿Ha parchado su sistema? | ¿Necesitas cambiar de contraseña? | ¿Qué ha dicho la compañía acerca del problema? | |
|---|---|---|---|---|
| Apple | No queda claro | No queda claro | No queda claro | Apple no se ha manifestado. |
| Amazon | No | No | No | «Amazon.com is not affected.» |
| Si | Si | Si* | “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. | |
| Microsoft | No | No | No | Los servicios de Microsoft no funcionan con OpenSSL, por lo que no estan afectados. |
| Yahoo | Si | Si | Si | «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. |
| ¿Fué afectado? | ¿Ha parchado su sistema? | ¿Necesitas cambiar de contraseña? | ¿Qué ha dicho la compañía acerca del problema? | |
|---|---|---|---|---|
| Gmail | Si | Si | Recomendable* | “We have assessed the SSL vulnerability and applied patches to key Google services.” *Google said que los usuarios no necesitan cambiar sus contraseñas, pero mejor prevenir que lamentar. |
| Hotmail / Outlook | No | No | No | Los servicios de Microsoft no funcionan con OpenSSL, por lo que no estan afectados. |
| Yahoo Mail | Si | Yes | Si | «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.» |
| ¿Fué afectado? | ¿Ha parchado su sistema? | ¿Necesitas cambiar de contraseña? | ¿Qué ha dicho la compañía acerca del problema? | |
|---|---|---|---|---|
| Amazon | No | No | No | «Amazon.com is not affected.» |
| Amazon Web Services(for website operators) | Si | Si | Si | 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. |
| eBay | No queda claro | No queda claro | No | eBay initially said, «The vast majority of our services were not impacted and our users can continue to shop securely on our marketplace.» They later added, «When you login to eBay using your user name and password these details were not exposed to the OpenSSL vulnerability.» |
| GoDaddy | Si | Si | Si | «We’ve been updating GoDaddy services that use the affected OpenSSL version.» Full Statement |
| PayPal | No | No | No | «Your PayPal account details were not exposed in the past and remain secure.» Full Statement |
| ¿Fué afectado? | ¿Ha parchado su sistema? | ¿Necesitas cambiar de contraseña? | ¿Qué ha dicho la compañía acerca del problema? | |
|---|---|---|---|---|
| Dropbox | Si | Si | Si | «We’ve patched all of our user-facing services & will continue to work to make sure your stuff is always safe.» |
| Evernote | No | No | No | «Evernote’s service, Evernote apps, and Evernote websites … all use non-OpenSSL implementations of SSL/TLS to encrypt network communications.»Full Statement |
| Minecraft | Si | Si | Si | «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 | No queda claro | No queda claro | No queda claro | «Like many companies, we took immediate action to assess the vulnerability and address it. We are not aware of any customer impact.» |
| SoundCloud | Si | Si | Si | SoundCloud emphasized that there were no indications of any foul play and that the company’s actions were simply precautionary. |
Vía Mashable
