Slashdot Mirror

← Back to Stories (view on slashdot.org)

One Month Later: 300,000 Servers Remain Vulnerable To Heartbleed

Posted by Soulskill on from the server-security-hipsters-don't-follow-the-crowd dept.

DavidGilbert99 writes: "The Heartbleed Bug cause widespread panic from internet users around the world worried their sensitive information was being targeted. While system administrators were warned to patch their systems, a security researcher notes that 300,000 servers remain vulnerable to the heartbleed flaw a full month later. He said, 'Last month, I found 1-million systems supporting the "heartbeat" feature (with one third patched). This time, I found 1.5-million systems supporting the "heartbeat" feature, with all but the 300k patched. This implies to me that the first response to the bug was to disable heartbeats, then later when people correctly patched the software, heartbeats were re-enabled. Note that only OpenSSL supports heartbeats, meaning that the vast majority of SSL-supporting servers are based on software other than OpenSSL.' A developer at Vivaldi Technologies AS also pointed out that a significant number of server administrators botched their response, going from safe to vulnerable."

10 of 60 comments (clear)

  1. Re:fp by TWX · · Score: 3, Funny

    Woo - first :p

    If this is what you have to do to be happy, my heart bleeds for you...

    --
    Do not look into laser with remaining eye.
  2. Certificate extortion by Scutter · · Score: 5, Interesting

    What would help is if there were some certificate system that didn't rely on extortion or exorbitant prices. I know several admins that mitigated the hole but couldn't replace their certificates either because the signer charges a ridiculous revocation fee (I'm looking at you, StartSSL), or because the cost of cutting and signing new certificates was too high. We need a better trust system.

    --

    "Tell me doctor, with all of your defenses, are there any provisions for an attack by killer bees?"
  3. 12 of those are mine. by hawguy · · Score: 3, Interesting

    We have are 12 dev/test servers that I didn't bother to patch because they'll be decommissioned in a month or two along with the rest of the datacenter they are in, and even though they support SSL connections (with a disposable cert from our private CA), they are generally only used with HTTP and have no private data to protect, and are almost completely unused now.

    If someone wants to spend time trying to steal the server's private key or steal user data from the server, that's fine with me, I'd rather have them spend time on my disposable server than someone's real server.

  4. Safe to vulnerable by jrumney · · Score: 3, Interesting

    A developer at Opera Software also pointed out that a significant number of server administrators botched their response, going from safe to vulnerable.

    I'm guessing a lot of these are going to be people running older stable distributions that were running versions of OpenSSL from before the bug was introduced. On hearing the news, they may have quickly looked to see if there was an upgrade, seen that there was not, and either installed a newer rpm/deb they found somewhere, or downloaded the latest source they could find (in a source repository for their distro perhaps) and built from source. Meanwhile the patch for the bug had only just been checked into git.

  5. The SSL problems. by jellomizer · · Score: 4, Insightful

    I am not a systems administrator (I am a software designer, when I do administration it requires a lot of trail and error.), I do however have to setup an SSL site once every few years. And because of the rarity of this action this is one of those jobs that are difficult to do, compared to other jobs. Sure if your web browser is installed via an Apt-get you are good. However there are times where you need to install it manually, and then you fight and tinker until SSL works, when it does work, your tendency is not to tinker with it anymore.
    The issue with Heart Bleed is that it effects open SSL, one of the trouble maker libraries, that require more then just the Basic make config & make & make install.

    Now there are a lot of sites setup my armature system admins, many who are less technical then I am, who will get it going and let it run. There isn't any enterprise architecture, the web site is running on a single PC with a single hard drive, chances are the hard drive had already died, and the site is just running from active memory.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  6. Let me expose my ignorance... by swb · · Score: 4, Insightful

    As I understand this, a vulnerable server can expose its private SSL key to an attacker. With this private key, I can decrypt all of its encrypted SSL traffic.

    This correct so far?

    Now, as I understand this so far, having the private key is great, but I need to be able to MITM the connection to decrypt anything.

    How hard is this? At the transport layer, this would require snooping the network connection of the server; someplace locally on the LAN (easiest, port mirror, maybe) or at the ISP (harder, maybe less likely).

    The other option would be some kind of DNS spoofing/vulnerability/cache poisoning, redirecting all the server traffic to a system I controlled and then piping it back out. How likely is this?

    1. Re:Let me expose my ignorance... by Qzukk · · Score: 3, Insightful

      a vulnerable server can expose its private SSL key to an attacker

      A vulnerable server can expose anything in the server process's memory space to the attacker. Obligatory: http://xkcd.com/1354/

      --
      If I have been able to see further than others, it is because I bought a pair of binoculars.
    2. Re:Let me expose my ignorance... by Dagger2 · · Score: 3, Interesting

      As I understand this, a vulnerable server can expose its private SSL key to an attacker. With this private key, I can decrypt all of its encrypted SSL traffic.

      As already mentioned, it's anything in the server's memory. Or the client's, since Heartbleed affects clients too.

      Now, as I understand this so far, having the private key is great, but I need to be able to MITM the connection to decrypt anything.

      It depends whether the connection is using perfect forward secrecy or not. If it's using PFS, then you need an active MITM to grab the session keys, so you can't decrypt old captured traffic and you need to keep your MITM up for new traffic. If there's no PFS, then all traffic ever sent with a given SSL cert can be decrypted with access to that cert's private key. All you need is to passively sniff it, then store it for later on the off-chance you ever get (or crack) the key.

      (I'm going to write a small essay on this, because it's important but very poorly documented on the web.)

      Given that, you'd think PFS would be common, but according to this study it's only available on 60-70% of web servers (they don't give a precise number, just 60% that support DHE and 18% that support ECDHE, but those two sets overlap), of which 80% prefer to use cipher suites without PFS, so about half of webservers either don't support PFS or typically won't use it. Slashdot doesn't, for example. Neither does microsoft.com. I guess that's just the homepage, but then windowsupdate.microsoft.com doesn't use it either. It's not supported on outlook.com's web, IMAP, POP3, or SMTP servers. addons.mozilla.org and marketplace.firefox.com also join the club, but their main website and the Firefox update sites do PFS at least. I couldn't find a Google property that didn't do PFS.

      And on top of that, of those sites that do use it, 99.3% use 1024-bit DH parameters, which essentially lowers the length of their RSA keys to 1024 bits (which affects the 80% of sites with 2048-bit or longer RSA keys).

      If you want to make sure you're actually using PFS, and with decent DH parameters, you generally need to make sure to configure it. Apache does this for you automatically from 2.4.7 onwards (before that, it'll use PFS but only with 1024-bit DH parameters). A lot of other software requires being fed DH parameters manually -- for instance, Courier's IMAP/SMTP servers, ZNC, ircd-hybrid etc. (And when was the last time you configured DH parameters for a server?)

      You can check if any given connection supports PFS by looking at the cipher suite in use. If it starts with DHE or ECDHE, it has PFS. (The "E" at the end stands for ephemeral; if it says DH, ECDH, or doesn't mention either of those, then there's no PFS). You can check with e.g. CipherFox in Firefox, or using the openssl command-line tools:

      $ openssl s_client -connect www.debian.org:443 | grep Cipher
              Cipher : DHE-RSA-AES256-GCM-SHA384

      If you point it at servers you use regularly, you'll probably be pretty depressed at the results. I know I was when I was making that list above...

  7. Re:Browser plug-in by crow · · Score: 3, Informative

    Thanks! I see there's also one for Chrome:

    https://chrome.google.com/webs...

    I just hope these plugins are trustworthy.

  8. Re:We can't patch yet... by Penguinisto · · Score: 4, Informative

    ...because we're waiting for vendors to issue patches.

    1) who is the "we" you refer to? 9 times out of 10, there are workarounds, ranging from shutting off the heartbeat feature in OpenSSL to parking an SSL proxy host or load-balancer (depending on application) in-between your affected box and the rest of the planet. And yes, it's that fucking important.

    2) The "new, latest security hole" in this instance can turn your company's reputation and sales into rancid mush should you get compromised, and in this case, there's no easy way to catch it before they get in. Oh, and don't ask about the potential for lawsuits that a data breach can generate from pissed-off customers.

    3) If a vendor hasn't coughed up a fix by now? Stop using the product, and/or learn enough about it to wedge in your own fix until you can replace the product with something whose vendor is more responsive.

    4) Sibling isn't entirely flamebait... a competent sysadmin is more than just a keyboard button actuator - he/she should have enough technical mojo to cook up a means to help protect his career and his company in cases like this. If one of my admins told me what you just wrote without providing solid proof that no workaround exists, I'd sit him down and ask him if he really wants to continue his career as a sysadmin.

    --
    Quo usque tandem abutere, Nimbus, patientia nostra?