[Cerowrt-devel] CVE-2014-0160 : heartbleed CVE on openssl - http://heartbleed.com/

[Cerowrt-devel] CVE-2014-0160 : heartbleed CVE on openssl - http://heartbleed.com/

[Dave Taht]

This one looks pretty nasty.

see http://lwn.net/Articles/593683/ for more details.

The headache and cost of updating all the gear I maintain is insanely high.

Some of my OSes are so old as to no longer have updates, others have ssl certs
that I can now no longer trust for email or imap, still others work on
the vpn... and I only have a few dozen machines to fix, personally.

On the boxes I can update I see a whole bunch of new certs coming down
and it looks like ubuntu 13.10 has an update for sure...

(I feel for those with thousands or more services to patch.)

In cerowrt's case I cannot easily go back and rebuild a "stable" release, and
the vulnerability is limited (with the default package set) to the
admin web interface, which is by default limited to the local
interfaces...

... and by default we use perfect forward secrecy...

... and an attacker would want to read mips data

so the immediate vulnerabilities for cero are small.

but if this CVE is bad as it looks, vast chunks of the internet are
vulnerable, certs stolen, usernames and passwords exposed, end-sites
not trustable, etc, etc.

Cryptogeddon.






-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article

Re: [Cerowrt-devel] CVE-2014-0160 : heartbleed CVE on openssl - http://heartbleed.com/

[Stephen Hemminger]

On Mon, 7 Apr 2014 18:38:58 -0700
Dave Taht <dave.taht@gmail.com> wrote:

> This one looks pretty nasty.
> 
> see http://lwn.net/Articles/593683/ for more details.
> 
> The headache and cost of updating all the gear I maintain is insanely high.
> 
> Some of my OSes are so old as to no longer have updates, others have ssl certs
> that I can now no longer trust for email or imap, still others work on
> the vpn... and I only have a few dozen machines to fix, personally.

Actually, not as bad as it looks. The old OS's did not get more recent
versions of OpenSSL which have the bug. So in this case lazy vendors win out.


From heartbleed.com:
Some operating system distributions that have shipped with potentially vulnerable OpenSSL version:

Debian Wheezy (stable), OpenSSL 1.0.1e-2+deb7u4
Ubuntu 12.04.4 LTS, OpenSSL 1.0.1-4ubuntu5.11
CentOS 6.5, OpenSSL 1.0.1e-15
Fedora 18, OpenSSL 1.0.1e-4
OpenBSD 5.3 (OpenSSL 1.0.1c 10 May 2012) and 5.4 (OpenSSL 1.0.1c 10 May 2012)
FreeBSD 10.0 - OpenSSL 1.0.1e 11 Feb 2013
NetBSD 5.0.2 (OpenSSL 1.0.1e)
OpenSUSE 12.2 (OpenSSL 1.0.1c)

Operating system distribution with versions that are not vulnerable:

Debian Squeeze (oldstable), OpenSSL 0.9.8o-4squeeze14
SUSE Linux Enterprise Server
FreeBSD 8.4 - OpenSSL 0.9.8y 5 Feb 2013
FreeBSD 9.2 - OpenSSL 0.9.8y 5 Feb 2013
FreeBSD Ports - OpenSSL 1.0.1g (At 7 Apr 21:46:40 2014 UTC)