itsallwater wrote:
However it might be pointless (so I've
read) changing passwords. Because it's also likely they* have the SSL Certificate keys too, using this exploit.
No , its *possible* , when you perform the exploit you get a random block of memory - its possible for someone to spend hours / days / weeks hitting a vulnerable server and never getting anything useful and its also possible for someone to hit a vulnerable server once and get passwords / keys / credit card information.
The information collected cannot be targeted in any way you just get a random chunk of data from the machine and thats what you get - if you run it again you get another random chunk
Anyone who is running a server thats affected by this should also bin their SSL certificates and create new ones to be 'safe' and I expect any large companies to do this
Here is one of the (many) emails I have from one company on how they handled it
Quote:
How we fixed the Heartbleed bug
How we fixed the Heartbleed bug
As you opened up Wunderlist today, you would have noticed that you had been logged out. We did this to protect your data against an internet-wide security vulnerability called ‘Heartbleed’. Heartbleed affects the OpenSSL framework which is used by many websites to privately send data to and from an internet server.
For you, this now means you’ll have to simply log back into Wunderlist. We also strongly recommend that you reset your password for Wunderlist.
We want you to know, that we’ve made Wunderlist’s Sync Service completely safe from Heartbleed, and this is how we’ve kept your data safe and sound:
As soon as we were made aware of Heartbleed, we protected your data by preemptively turning off our Sync Service, eliminating any potential security breaches by stopping all communication to our servers.
We deployed the updated OpenSSL libraries.
We then renewed all of our SSL certificates.
We logged out all users to ensure that everyone would create new, secure connections.
Want to know more?
If you have any questions or want to learn more, please take a read of our in-depth article at the Wunderlist Support Center. Also, one of our engineers, Duncan Davidson, has written a personal account of what happened in more technical detail.
Links :
http://support.wunderlist.com/customer/ ... april-2014https://medium.com/p/804cdf4b48c1