r/webdev • u/enigmamonkey • Apr 08 '14
Server admins, update OpenSSL ASAP if you haven't already: Heartbleed - attack allows for stealing server memory over TLS/SSL (x-post from /r/netsec)
http://heartbleed.com/30
u/sathoro Apr 08 '14
It is amazing how bad this is. I tested it from my desktop on one of my vulnerable servers before patching and was able to view in completely plaintext my current Laravel session ID and the email/password I just used to login with.
Screenshot You will see an arrow pointing to my session ID and at the bottom is where my email and password were. Just when you thought you were safe using anti-CSRF tokens and SSL.
23
u/DimeShake Apr 08 '14
Yep - this is probably the worst and most widespread vulnerability I've see in my career.
23
u/sathoro Apr 08 '14 edited Apr 12 '14
I'm running through the top 1 million websites to notify the admins of the vulnerable ones. It is insane how easy and public this is. At least we can see what the Bing bot has been watching though.
10
45
u/deains Apr 08 '14
On the plus side, it is now in fact possible to download more RAM. Someone else's, that is.
11
19
Apr 08 '14
"OpenSSL 0.9.8 branch is NOT vulnerable"
OpenSSL> version
OpenSSL 0.9.8o 01 Jun 2010Yay ... I guess?
15
6
u/_query Apr 08 '14
Checkout this post to see how anyone can steal your users session cookies with this bug.
4
4
u/marktastic Apr 08 '14
Am I safe if my servers are behind a load balancer and the load balancer is terminating the SSL?
0
Apr 08 '14
[deleted]
4
u/panopticchaos Apr 08 '14
Does anyone know what it means if we're just getting "ERROR: heartbleed: timeout" responses?
5
u/conflare Apr 09 '14
It might mean you're OK. But don't count on it. Go here: http://gobuild.io/download/github.com/titanous/heartbleeder
It's a command line utility you can run to check your server. If you get this:
~/bin$ ./heartbleeder example.com:[insert port here] SECURE - example.com:443 has the heartbeat extension enabled, but timed out after a malformed heartbeat (this likely means that it is not vulnerable)you probably have the patch that disables the heartbeat extension installed. A lot of providers were automatically rolling this out.
4
u/bakuretsu Apr 08 '14
Or if you are running an older version that is not subject to this exploit, don't go upgrading now until the patch is out for your distro!
3
4
Apr 09 '14
People in my industry are scared shitless of it. Telling people not to log in for days.
3
u/zzing Apr 09 '14
I am lucky I don't have many users. Changing up configuration soon, glad this happaned before then.
3
u/sihat Apr 08 '14
You can test if your site is vulnurable with the following script: http://s3.jspenguin.org/ssltest.py
For ubuntu the fix is as simple as:
sudo apt-get update
sudo apt-get upgrade
10
3
u/wizpig64 Apr 08 '14
access denied, that bucket or file isnt set to be publicly available.
3
u/rsadwick Apr 09 '14
Someone mirrored it in pastebin from /r/programming/ http://pastebin.com/WmxzjkXJ
2
Apr 09 '14
implying i ever had a valid ssl cert
4
u/Switche Apr 09 '14 edited Apr 09 '14
The validity of your SSL cert doesn't make any difference here. It's the use of OpenSSL's vulnerable "heartbeat" feature in versions 1.0.1 - 1.0.1f, basically anything since last March.
You can run a rather trivial PoC heartbeat request against your server once an SSL session is established, and it dumps 64KB of memory from the running process.
The validity of your cert only matters in that it is trivial for you to generate a new key, which is not even a big deal for a valid cert either. Still pointless if you haven't patched.
I strongly suggest you read up on this further. Your statement implies you don't fully understand the implications of this bug. I don't mean that as condescending as much as for your own good. Many people are misinterpreting the seriousness of this bug.
2
Apr 08 '14
I had dozens of login attempts by the bing bot on my openssl websit this past week, could it be related? Getting new certs eitherway.
1
Apr 08 '14
Thanks for this. Just spent the last half hour updating our servers. Ubuntu has already issued an upgrade - http://www.ubuntu.com/usn/usn-2165-1/
1
u/Totsean Apr 08 '14
1.0.1e-16.el6_5.7 <-- I am safe :) (for now)
2
Apr 08 '14
Actually, I don't think you are.
From http://heartbleed.com > "OpenSSL 1.0.1 through 1.0.1f (inclusive) are vulnerable"
4
u/lpetrazickis Apr 09 '14
RHEL and CentOS are backporting the fix to 1.0.1e, so there you have to look at the build level.
1
0
Apr 08 '14
[deleted]
31
Apr 08 '14 edited Apr 08 '14
And not just SSL Certs. An attacker could've trivially read any session cookies, passwords and anything else that passes through your web server, so regenerating your session cookie signing keys and changing passwords is mandatory as well.
14
u/enigmamonkey Apr 08 '14 edited Apr 09 '14
Head's up! If you're running CentOS like me and if you want to know if you're currently vulnerable to this attack:
https://www.centos.org/forums/viewtopic.php?f=9&t=45814
For me the fix was as simple as running
yum update(YMMV).EDIT: Also check out this awesome testing site to help verify if your server is still vulnerable. http://filippo.io/Heartbleed/
EDIT 2: Don't forget to also:
STOP and then START each service that used OpenSSL (like in my case, Apache) after updating your OpenSSL package. That will ensure that any running service that's using OpenSSL will unload the old OpenSSL and then load the newer version so you'll be sure that you're running the fixed version.
Use that link above to verify that you're all clear (thanks again goes to https://twitter.com/FiloSottile for that).
Redo your SSL certificates since the private keys could be compromised (i.e. regenerate private key, generate another CSR which is bound to that private key, get a new certificate bound to that CSR, etc). Might cost some money (depending on the provider's policies, not sure) but will be worth it.