OpenSSL Security Advisory

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
37 messages Options
12
Reply | Threaded
Open this post in threaded view
|

OpenSSL Security Advisory

openssl
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

OpenSSL Security Advisory [07 Apr 2014]
========================================

TLS heartbeat read overrun (CVE-2014-0160)
==========================================

A missing bounds check in the handling of the TLS heartbeat extension can be
used to reveal up to 64k of memory to a connected client or server.

Only 1.0.1 and 1.0.2-beta releases of OpenSSL are affected including
1.0.1f and 1.0.2-beta1.

Thanks for Neel Mehta of Google Security for discovering this bug and to
Adam Langley <[hidden email]> and Bodo Moeller <[hidden email]> for
preparing the fix.

Affected users should upgrade to OpenSSL 1.0.1g. Users unable to immediately
upgrade can alternatively recompile OpenSSL with -DOPENSSL_NO_HEARTBEATS.

1.0.2 will be fixed in 1.0.2-beta2.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJTQt1bAAoJENNXdQf6QOniGhkP/AjjZgV+g7ZyxnxdnvA2+sdV
sxNso208Cod8DKnDONtXHuPTkTFfyHl72FM1ea99woe3X6JWj3PyiZGvSfeo4Jj/
QiDJvvcHc5Xq00gAr6MIarhMJbRtYkM+Th6PPXyqODYcb/pDoqy5VWo/R9QkZTPn
zaiXPyapJB/qSYo4UqXWerT9YTLdYmiro//kQN0U/SedF/fNz4CEBcMyz6z7YJAC
LFoE6Vf54PAkNvxjcX9ugIKluBMk5YONRG8PB0X/UDwf9Kj4L6OTT51x1yeFw3Sg
GzTqvKD+2JWzFDCcfJULRCSCEwHhKbjR7n3sI1RPaaEWp5E63+9HSMRYjVOFIwt/
OTrMPbW1BEiX0A7NB7HSrrvddnYd3sz8A44v00oesr+XaW5nyu79IndQwLhPkKYF
Dkb67quw/tfV6Y1r4sETqSd2FrM7MpFzltywMKzVKWNpMSwOAWSBGUl7VH0m84Ty
zAufUSEnYIA3dMC2DnHie+ot4WnjJlTErBmfUb/QNbNYDt0vjhS60oydP1NJ8AlG
aoUK7mslOlVCauAIeGNbi4PzJ+LvWYmyFFGT+M1/UOBZFFvG7jsReBjTIu9dg3Za
S7NE7CeMvRRpOEm1+T9L8a26/c6C9dwF7JPQvMpTR3BeT2jjkYe8rdTCkT91g1sd
J37YgDNuefzrsA+B5/o7
=szjb
-----END PGP SIGNATURE-----
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: OpenSSL Security Advisory

monloi perez
Hi,

Is OpenSSL 0.9.7d  vulnerable? Can seem to confirm based on the list of affected services from this site http://heartbleed.com/.

Regards,
Mon

On Tuesday, April 8, 2014 3:01 AM, OpenSSL <[hidden email]> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

OpenSSL Security Advisory [07 Apr 2014]
========================================

TLS heartbeat read overrun (CVE-2014-0160)
==========================================

A missing bounds check in the handling of the TLS heartbeat extension can be
used to reveal up to 64k of memory to a connected client or server.

Only 1.0.1 and 1.0.2-beta releases of OpenSSL are affected including
1.0.1f and 1.0.2-beta1.

Thanks for Neel Mehta of Google Security for discovering this bug and to
Adam Langley <[hidden email]> and Bodo Moeller <[hidden email]> for
preparing the fix.

Affected users should upgrade to OpenSSL 1.0.1g. Users unable to immediately
upgrade can alternatively recompile OpenSSL with -DOPENSSL_NO_HEARTBEATS.

1.0.2 will be fixed in 1.0.2-beta2.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJTQt1bAAoJENNXdQf6QOniGhkP/AjjZgV+g7ZyxnxdnvA2+sdV
sxNso208Cod8DKnDONtXHuPTkTFfyHl72FM1ea99woe3X6JWj3PyiZGvSfeo4Jj/
QiDJvvcHc5Xq00gAr6MIarhMJbRtYkM+Th6PPXyqODYcb/pDoqy5VWo/R9QkZTPn
zaiXPyapJB/qSYo4UqXWerT9YTLdYmiro//kQN0U/SedF/fNz4CEBcMyz6z7YJAC
LFoE6Vf54PAkNvxjcX9ugIKluBMk5YONRG8PB0X/UDwf9Kj4L6OTT51x1yeFw3Sg
GzTqvKD+2JWzFDCcfJULRCSCEwHhKbjR7n3sI1RPaaEWp5E63+9HSMRYjVOFIwt/
OTrMPbW1BEiX0A7NB7HSrrvddnYd3sz8A44v00oesr+XaW5nyu79IndQwLhPkKYF
Dkb67quw/tfV6Y1r4sETqSd2FrM7MpFzltywMKzVKWNpMSwOAWSBGUl7VH0m84Ty
zAufUSEnYIA3dMC2DnHie+ot4WnjJlTErBmfUb/QNbNYDt0vjhS60oydP1NJ8AlG
aoUK7mslOlVCauAIeGNbi4PzJ+LvWYmyFFGT+M1/UOBZFFvG7jsReBjTIu9dg3Za
S7NE7CeMvRRpOEm1+T9L8a26/c6C9dwF7JPQvMpTR3BeT2jjkYe8rdTCkT91g1sd
J37YgDNuefzrsA+B5/o7
=szjb
-----END PGP SIGNATURE-----
______________________________________________________________________
OpenSSL Project                                http://www.openssl.org
Announcement Mailing List                [hidden email]
Automated List Manager                          [hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: OpenSSL Security Advisory

Alan Buxey
https://www.openssl.org/news/changelog.html

1.0.1 introduced the heartbeat support.

1.0.0 and earlier are fortunate in that they didnt have it.....but then they didnt have things to stop you from being BEASTed so some you win, some you lose. ;)

alan
Reply | Threaded
Open this post in threaded view
|

Re: OpenSSL Security Advisory

monloi perez
True. Thanks for the quick reply.

On Wednesday, April 9, 2014 3:33 PM, Alan Buxey <[hidden email]> wrote:
https://www.openssl.org/news/changelog.html

1.0.1 introduced the heartbeat support.

1.0.0 and earlier are fortunate in that they didnt have it.....but then they didnt have things to stop you from being BEASTed so some you win, some you lose. ;)

alan


Reply | Threaded
Open this post in threaded view
|

Re: OpenSSL Security Advisory

Ted Byers
In reply to this post by openssl
How do I determine whether or not the web servers I run are affected?  They are Apache 2.4, built for 64 bit Windows and downloaded from Apachelounge.  I have no idea what version of openssl it was built with.  Does anyone here know if the feature that introduces the risk can be turned off, without introducing other risks?  If so, how?

Also, could the security keys we bought have been compromised?

Any advice on how I can protect my servers better would be appreciated.

Thanks

Ted

--
R.E.(Ted) Byers, Ph.D.,Ed.D.


On Mon, Apr 7, 2014 at 4:31 PM, OpenSSL <[hidden email]> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

OpenSSL Security Advisory [07 Apr 2014]
========================================

TLS heartbeat read overrun (CVE-2014-0160)
==========================================

A missing bounds check in the handling of the TLS heartbeat extension can be
used to reveal up to 64k of memory to a connected client or server.

Only 1.0.1 and 1.0.2-beta releases of OpenSSL are affected including
1.0.1f and 1.0.2-beta1.

Thanks for Neel Mehta of Google Security for discovering this bug and to
Adam Langley <[hidden email]> and Bodo Moeller <[hidden email]> for
preparing the fix.

Affected users should upgrade to OpenSSL 1.0.1g. Users unable to immediately
upgrade can alternatively recompile OpenSSL with -DOPENSSL_NO_HEARTBEATS.

1.0.2 will be fixed in 1.0.2-beta2.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJTQt1bAAoJENNXdQf6QOniGhkP/AjjZgV+g7ZyxnxdnvA2+sdV
sxNso208Cod8DKnDONtXHuPTkTFfyHl72FM1ea99woe3X6JWj3PyiZGvSfeo4Jj/
QiDJvvcHc5Xq00gAr6MIarhMJbRtYkM+Th6PPXyqODYcb/pDoqy5VWo/R9QkZTPn
zaiXPyapJB/qSYo4UqXWerT9YTLdYmiro//kQN0U/SedF/fNz4CEBcMyz6z7YJAC
LFoE6Vf54PAkNvxjcX9ugIKluBMk5YONRG8PB0X/UDwf9Kj4L6OTT51x1yeFw3Sg
GzTqvKD+2JWzFDCcfJULRCSCEwHhKbjR7n3sI1RPaaEWp5E63+9HSMRYjVOFIwt/
OTrMPbW1BEiX0A7NB7HSrrvddnYd3sz8A44v00oesr+XaW5nyu79IndQwLhPkKYF
Dkb67quw/tfV6Y1r4sETqSd2FrM7MpFzltywMKzVKWNpMSwOAWSBGUl7VH0m84Ty
zAufUSEnYIA3dMC2DnHie+ot4WnjJlTErBmfUb/QNbNYDt0vjhS60oydP1NJ8AlG
aoUK7mslOlVCauAIeGNbi4PzJ+LvWYmyFFGT+M1/UOBZFFvG7jsReBjTIu9dg3Za
S7NE7CeMvRRpOEm1+T9L8a26/c6C9dwF7JPQvMpTR3BeT2jjkYe8rdTCkT91g1sd
J37YgDNuefzrsA+B5/o7
=szjb
-----END PGP SIGNATURE-----
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]



Reply | Threaded
Open this post in threaded view
|

Re: OpenSSL Security Advisory

Ali Jawad


On Wed, Apr 9, 2014 at 2:05 PM, Ted Byers <[hidden email]> wrote:
How do I determine whether or not the web servers I run are affected?  They are Apache 2.4, built for 64 bit Windows and downloaded from Apachelounge.  I have no idea what version of openssl it was built with.  Does anyone here know if the feature that introduces the risk can be turned off, without introducing other risks?  If so, how?

Also, could the security keys we bought have been compromised?

Any advice on how I can protect my servers better would be appreciated.

Thanks

Ted

--
R.E.(Ted) Byers, Ph.D.,Ed.D.


On Mon, Apr 7, 2014 at 4:31 PM, OpenSSL <[hidden email]> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

OpenSSL Security Advisory [07 Apr 2014]
========================================

TLS heartbeat read overrun (CVE-2014-0160)
==========================================

A missing bounds check in the handling of the TLS heartbeat extension can be
used to reveal up to 64k of memory to a connected client or server.

Only 1.0.1 and 1.0.2-beta releases of OpenSSL are affected including
1.0.1f and 1.0.2-beta1.

Thanks for Neel Mehta of Google Security for discovering this bug and to
Adam Langley <[hidden email]> and Bodo Moeller <[hidden email]> for
preparing the fix.

Affected users should upgrade to OpenSSL 1.0.1g. Users unable to immediately
upgrade can alternatively recompile OpenSSL with -DOPENSSL_NO_HEARTBEATS.

1.0.2 will be fixed in 1.0.2-beta2.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJTQt1bAAoJENNXdQf6QOniGhkP/AjjZgV+g7ZyxnxdnvA2+sdV
sxNso208Cod8DKnDONtXHuPTkTFfyHl72FM1ea99woe3X6JWj3PyiZGvSfeo4Jj/
QiDJvvcHc5Xq00gAr6MIarhMJbRtYkM+Th6PPXyqODYcb/pDoqy5VWo/R9QkZTPn
zaiXPyapJB/qSYo4UqXWerT9YTLdYmiro//kQN0U/SedF/fNz4CEBcMyz6z7YJAC
LFoE6Vf54PAkNvxjcX9ugIKluBMk5YONRG8PB0X/UDwf9Kj4L6OTT51x1yeFw3Sg
GzTqvKD+2JWzFDCcfJULRCSCEwHhKbjR7n3sI1RPaaEWp5E63+9HSMRYjVOFIwt/
OTrMPbW1BEiX0A7NB7HSrrvddnYd3sz8A44v00oesr+XaW5nyu79IndQwLhPkKYF
Dkb67quw/tfV6Y1r4sETqSd2FrM7MpFzltywMKzVKWNpMSwOAWSBGUl7VH0m84Ty
zAufUSEnYIA3dMC2DnHie+ot4WnjJlTErBmfUb/QNbNYDt0vjhS60oydP1NJ8AlG
aoUK7mslOlVCauAIeGNbi4PzJ+LvWYmyFFGT+M1/UOBZFFvG7jsReBjTIu9dg3Za
S7NE7CeMvRRpOEm1+T9L8a26/c6C9dwF7JPQvMpTR3BeT2jjkYe8rdTCkT91g1sd
J37YgDNuefzrsA+B5/o7
=szjb
-----END PGP SIGNATURE-----
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]




Reply | Threaded
Open this post in threaded view
|

RE: OpenSSL Security Advisory

Eisenacher, Patrick
In reply to this post by Ted Byers
Hi Ted,

> -----Original Message-----
> From: [hidden email] [mailto:owner-openssl-
>
> How do I determine whether or not the web servers I run are affected?
> They are Apache 2.4, built for 64 bit Windows and downloaded from
> Apachelounge.  I have no idea what version of openssl it was built with.  Does
> anyone here know if the feature that introduces the risk can be turned off,
> without introducing other risks?  If so, how?

you can check for yourself:
- http://filippo.io/Heartbleed/
- http://possible.lv/tools/hb/
- https://github.com/noxxi/p5-scripts/blob/master/check-ssl-heartbleed.pl

> Also, could the security keys we bought have been compromised?

Certainly yes. You should replace them. I read today that some CAs offer free replacements.


HTH,
Patrick Eisenacher
:��I"Ϯ��r�m���� (���Z+�K�+����1���x ��h���[�z�(���Z+� ��f�y������f���h��)z{,���
Reply | Threaded
Open this post in threaded view
|

RE: OpenSSL Security Advisory

Salz, Rich
In reply to this post by Ted Byers

Ø  How do I determine whether or not the web servers I run are affected?

 

Here’s a simple way:

                echo B | openssl s_client –connect $HOST:$PORT

if you see “heartbeating” at the end, then $HOST is vulnerable.

 

How can you tell if private keys have been taken?  You can’t, really. You can estimate the likelihood by looking closely at how OpenSSL_Malloc() return values are used and layed out.  The risk is that an allocated ssl-record buffer is right up against a private key being stored.

 

                /r$

 

-- 

Principal Security Engineer

Akamai Technology

Cambridge, MA

 

Reply | Threaded
Open this post in threaded view
|

Re: OpenSSL Security Advisory

Ted Byers
In reply to this post by Eisenacher, Patrick

Thanks Patrick.

Apache lounge already has a patched release released.  So, once I deploy that, and get my certificates reissued, I ought to be OK.

Thanks

Ted



--
R.E.(Ted) Byers, Ph.D.,Ed.D.

On Wed, Apr 9, 2014 at 8:37 AM, Eisenacher, Patrick <[hidden email]> wrote:
Hi Ted,

> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]
>
> How do I determine whether or not the web servers I run are affected?
> They are Apache 2.4, built for 64 bit Windows and downloaded from
> Apachelounge.  I have no idea what version of openssl it was built with.  Does
> anyone here know if the feature that introduces the risk can be turned off,
> without introducing other risks?  If so, how?

you can check for yourself:
- http://filippo.io/Heartbleed/
- http://possible.lv/tools/hb/
- https://github.com/noxxi/p5-scripts/blob/master/check-ssl-heartbleed.pl

> Also, could the security keys we bought have been compromised?

Certainly yes. You should replace them. I read today that some CAs offer free replacements.


HTH,
Patrick Eisenacher


Reply | Threaded
Open this post in threaded view
|

Re: OpenSSL Security Advisory

Ted Byers
In reply to this post by Salz, Rich

Thanks Rich,

I have obtained the new, patched, release of Apache from Apache lounge, and applied the patch to one server, which the online services say fix the problem on it, but your simple way of checking still says heartbeating at the end.  Does that mean that the patch didn't truly work? 

I get the heartbeating message on both unpatched and patched servers.  Should that make me worry about the patched machines?

Thanks

Ted


--
R.E.(Ted) Byers, Ph.D.,Ed.D.


On Wed, Apr 9, 2014 at 9:54 AM, Salz, Rich <[hidden email]> wrote:

Ø  How do I determine whether or not the web servers I run are affected?

 

Here’s a simple way:

                echo B | openssl s_client –connect $HOST:$PORT

if you see “heartbeating” at the end, then $HOST is vulnerable.

 

How can you tell if private keys have been taken?  You can’t, really. You can estimate the likelihood by looking closely at how OpenSSL_Malloc() return values are used and layed out.  The risk is that an allocated ssl-record buffer is right up against a private key being stored.

 

                /r$

 

-- 

Principal Security Engineer

Akamai Technology

Cambridge, MA

 


Reply | Threaded
Open this post in threaded view
|

Re: OpenSSL Security Advisory

Viktor Dukhovni
On Wed, Apr 09, 2014 at 10:55:23AM -0400, Ted Byers wrote:

> I get the heartbeating message on both unpatched and patched servers.
> Should that make me worry about the patched machines?

No, unfortunately both patched and unpatched systems respond the
same way to valid heartbeat requests as send by s_client(1).

To detect a difference, you need to send invalid heartbeat requests
whose payload is shorter than promised.  If you patch a copy of the
source code for OpenSSL 1.0.1 as below, and build statically linked
and run "./apps/openssl s_client ..." from the build tree:

--- a/ssl/t1_lib.c
+++ b/ssl/t1_lib.c
@@ -2702,7 +2702,7 @@ tls1_heartbeat(SSL *s)
  /* Message Type */
  *p++ = TLS1_HB_REQUEST;
  /* Payload length (18 bytes here) */
- s2n(payload, p);
+ s2n(0x4000, p);
  /* Sequence number */
  s2n(s->tlsext_hb_seq, p);
  /* 16 random bytes */

then you can detect the difference.  Patched systems won't respond
to the malformed heartbeat request.  Replace "echo B | ...." with something
like:

    (sleep 10; echo B; sleep 10) | ...

to make sure that the handshake is complete by the time the request is sent,
and the client does not disconnect too quickly.

--
        Viktor.
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

RE: OpenSSL Security Advisory

Salz, Rich
In reply to this post by Ted Byers

Ø  I get the heartbeating message on both unpatched and patched servers.  Should that make me worry about the patched machines?

Not necessarily.  If they updated to the ‘g’ release, then they are doing buffer-overrun checking and you’re safe.  You can probably find out by connecting to your server (via s_client again) and seeing what it says in the server line, as in

                echo HEAD / HTTP/1.0 | openssl s_client –connect $HOST:$PORT

The server usually says things like “apache/2.0 openssl/1.0.1g …” and other modules that are bundled in.

 

To be safest, heartbeats should just be disabled.  Nobody really uses them.

                /r$

 

-- 

Principal Security Engineer

Akamai Technology

Cambridge, MA

Reply | Threaded
Open this post in threaded view
|

Re: OpenSSL Security Advisory

Matthias Apitz-4
In reply to this post by openssl
> ----- Forwarded message from "Salz, Rich" <[hidden email]> -----
>
> Date: Wed, 9 Apr 2014 09:54:25 -0400
> From: "Salz, Rich" <[hidden email]>
> To: "[hidden email]" <[hidden email]>
> Subject: RE: OpenSSL Security Advisory
>
> Ø  How do I determine whether or not the web servers I run are affected?
>
> Here's a simple way:
>                 echo B | openssl s_client -connect $HOST:$PORT
> if you see "heartbeating" at the end, then $HOST is vulnerable.
>
> How can you tell if private keys have been taken?  You can't, really. You can estimate the likelihood by looking closely at how OpenSSL_Malloc() return values are used and layed out.  The risk is that an allocated ssl-record buffer is right up against a private key being stored.
>
>                 /r$

Hello Rich,

Can you please post a "good" and a "bad" server example. I have tested a
lot of servers, including 'akamai.com', and they all show HEARTBEATING
at the end:

$ echo B | openssl s_client -connect akamai.com:https
...
    Verify return code: 20 (unable to get local issuer certificate)
    ---
    HEARTBEATING
    675358796:error:1413B16D:SSL routines:SSL_F_TLS1_HEARTBEAT:peer does
    not accept
    heartbearts:/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/t1_lib.c:2562:

Thanks for clarification.

        matthias

--
Sent from my FreeBSD netbook

Matthias Apitz, <[hidden email]>, http://www.unixarea.de/ f: +49-170-4527211
UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

RE: OpenSSL Security Advisory

Salz, Rich
> Can you please post a "good" and a "bad" server example. I have tested a lot of servers, including 'akamai.com', and they all show HEARTBEATING at the end:

Look at Victor's recent post about how to patch openssl/s_client to make your own test.  That's the simplest.  My example tests only for those who have disabled TLs heartbeats, which is the safest thing, but not necessarily the only thing, to do.


--  
Principal Security Engineer
Akamai Technology
Cambridge, MA

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: OpenSSL Security Advisory

Matthias Apitz-4
In reply to this post by openssl
> > -----Original Message-----
> > From: Matthias Apitz [mailto:[hidden email]]
> > Sent: Thursday, April 10, 2014 6:41 AM
> > To: Apitz,Matthias
> > Subject: Fwd: RE: OpenSSL Security Advisory
> >
> > ----- Forwarded message from "Salz, Rich" <[hidden email]> -----
> >
> > Date: Wed, 9 Apr 2014 15:43:28 -0400
> > From: "Salz, Rich" <[hidden email]>
> > To: "[hidden email]" <[hidden email]>
> > Subject: RE: OpenSSL Security Advisory
> >
> > > Can you please post a "good" and a "bad" server example. I have
> > tested a lot of servers, including 'akamai.com', and they all show
> > HEARTBEATING at the end:
> >
> > Look at Victor's recent post about how to patch openssl/s_client to
> > make your own test.  That's the simplest.  My example tests only
> > for those who have disabled TLs heartbeats, which is the safest
> > thing, but not necessarily the only thing, to do.
> >

Hello,

I have instrumented an openssl 1.0.1f as posted by Victor:

guru@hein:~/openssl-1.0.1f> diff ssl/t1_lib.c.unpatched
ssl/t1_lib.c
2671c2671
<       s2n(payload, p);
---
>       s2n(0x4000, p);

but I still see HEARTBEATING, for example even from www.openssl.org:

guru@hein:~/openssl-1.0.1f/apps> (sleep 3 ; echo B ; sleep 3) | ./openssl s_client -connect www.openssl.org:443
...
HEARTBEATING
DONE

Do I something wrong?

Thx

        matthias

--
Matthias Apitz               |  /"\ ASCII Ribbon Campaign: www.asciiribbon.org
E-mail: [hidden email]     |  \ / - No HTML/RTF in E-mail
WWW: http://www.unixarea.de/ |   X  - No proprietary attachments
phone: +49-170-4527211       |  / \ - Respect for open standards
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: OpenSSL Security Advisory

Rob Stradling
In reply to this post by Salz, Rich
On 09/04/14 20:43, Salz, Rich wrote:
>> Can you please post a "good" and a "bad" server example. I have tested a lot of servers, including 'akamai.com', and they all show HEARTBEATING at the end:
>
> Look at Victor's recent post about how to patch openssl/s_client to make your own test.  That's the simplest.

Simpler still...

https://gist.github.com/robstradling/10363389

It's based on what Viktor posted, but it works without patching the
OpenSSL library code.

To compile:
$ gcc -ansi -pedantic -o heartbleed heartbleed.c -lssl -lcrypto

Examples:
$ ./heartbleed www.ibm.com:443
NOT VULNERABLE (TLS Heartbeat extension not supported by the server)

$ ./heartbleed secure.comodo.net:443
NOT VULNERABLE (TLS Heartbeat extension supported by the server)

$ ./heartbleed mail.visservansolkema.nl:443
VULNERABLE!

--
Rob Stradling
Senior Research & Development Scientist
COMODO - Creating Trust Online
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: OpenSSL Security Advisory

Viktor Dukhovni
In reply to this post by Matthias Apitz-4
On Thu, Apr 10, 2014 at 10:57:35AM +0200, Matthias Apitz wrote:

> I have instrumented an openssl 1.0.1f as posted by Victor:
>
> guru@hein:~/openssl-1.0.1f> diff ssl/t1_lib.c.unpatched
> ssl/t1_lib.c
> 2671c2671
> <       s2n(payload, p);
> ---
> >       s2n(0x4000, p);
>
> but I still see HEARTBEATING, for example even from www.openssl.org:
>
> guru@hein:~/openssl-1.0.1f/apps> (sleep 3 ; echo B ; sleep 3) | ./openssl s_client -connect www.openssl.org:443
> ...
> HEARTBEATING
> DONE
>
> Do I something wrong?

That logs the request, you also need to see the reply...  With servers that
reply to the hearbeat you should see:

    ...
    HEARTBEATING
    read R BLOCK
    DONE

--
        Viktor.
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: OpenSSL Security Advisory

Walter H.
In reply to this post by Rob Stradling
On 10.04.2014 13:16, Rob Stradling wrote:
On 09/04/14 20:43, Salz, Rich wrote:
Can you please post a "good" and a "bad" server example. I have tested a lot of servers, including 'akamai.com', and they all show HEARTBEATING at the end:

Look at Victor's recent post about how to patch openssl/s_client to make your own test.  That's the simplest.

Simpler still...

https://gist.github.com/robstradling/10363389

It's based on what Viktor posted, but it works without patching the OpenSSL library code.


Hello,

I get a link error - the same es the 2nd comment mentions there;

how can I fix this?

Thanks,
Walter

--
Mit freundlichen Grüßen,
Best regards,
Mes salutations distinguées,

Ing. Walter Höhlhubmer         _/      _/  _/    _/
                              _/      _/  _/    _/
Lederergasse 47a/7           _/      _/  _/    _/
A-4020 Linz a. d. Donau     _/  _/  _/  _/_/_/_/
Austria/EUROPE             _/_/_/_/_/  _/    _/
                          _/_/  _/_/  _/    _/
(+43 664 / 951 83 72)    _/      _/  _/    _/


smime.p7s (7K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: OpenSSL Security Advisory

Steven Kneizys
The same issue when I tried to port over to windows, the ssl3_write_bytes is not exposed in the library.  There doesn't seem to be an easy workaround that I can see.

Steve...

On Fri, Apr 11, 2014 at 7:40 AM, Walter H. <[hidden email]> wrote:
On 10.04.2014 13:16, Rob Stradling wrote:
On 09/04/14 20:43, Salz, Rich wrote:
Can you please post a "good" and a "bad" server example. I have tested a lot of servers, including 'akamai.com', and they all show HEARTBEATING at the end:

Look at Victor's recent post about how to patch openssl/s_client to make your own test.  That's the simplest.

Simpler still...

https://gist.github.com/robstradling/10363389

It's based on what Viktor posted, but it works without patching the OpenSSL library code.


Hello,

I get a link error - the same es the 2nd comment mentions there;

how can I fix this?

Thanks,
Walter

--
Mit freundlichen Grüßen,
Best regards,
Mes salutations distinguées,

Ing. Walter Höhlhubmer         _/      _/  _/    _/
                              _/      _/  _/    _/
Lederergasse 47a/7           _/      _/  _/    _/
A-4020 Linz a. d. Donau     _/  _/  _/  _/_/_/_/
Austria/EUROPE             _/_/_/_/_/  _/    _/
                          _/_/  _/_/  _/    _/
<a href="tel:%28%2B43%20664%20%2F%20951%2083%2072" value="+436649518372" target="_blank">(+43 664 / 951 83 72)    _/      _/  _/    _/




--
Steve Kneizys
Senior Business Process Engineer
Voice: <a href="tel:%28610%29%20256-1396" value="+16102561396" target="_blank">(610) 256-1396  [For Emergency Service <a href="tel:%28888%29864-3282" value="+18888643282" target="_blank">(888)864-3282]
Ferrilli Information Group -- Quality Service and Solutions for Higher Education
web: http://www.ferrilli.com/

Making you a success while exceeding your expectations.
Reply | Threaded
Open this post in threaded view
|

RE: OpenSSL Security Advisory

Jaaron Anderson
In reply to this post by Walter H.

Also try your range here
https://ssltools.websecurity.symantec.com/checker/views/certCheck.jsp
Hth
jaa


-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Walter H.
Sent: Friday, April 11, 2014 7:40 AM
To: [hidden email]
Subject: Re: OpenSSL Security Advisory

On 10.04.2014 13:16, Rob Stradling wrote:

        On 09/04/14 20:43, Salz, Rich wrote:
       

                        Can you please post a "good" and a "bad" server
example. I have tested a lot of servers, including 'akamai.com', and they
all show HEARTBEATING at the end:
                       


                Look at Victor's recent post about how to patch
openssl/s_client to make your own test.  That's the simplest.
               


        Simpler still...
       
        https://gist.github.com/robstradling/10363389 
       
        It's based on what Viktor posted, but it works without patching the
OpenSSL library code.
       
       
       

Hello,

I get a link error - the same es the 2nd comment mentions there;

how can I fix this?

Thanks,
Walter


--

Mit freundlichen Grüßen,
Best regards,
Mes salutations distinguées,

Ing. Walter Höhlhubmer         _/      _/  _/    _/
                              _/      _/  _/    _/
Lederergasse 47a/7           _/      _/  _/    _/
A-4020 Linz a. d. Donau     _/  _/  _/  _/_/_/_/
Austria/EUROPE             _/_/_/_/_/  _/    _/
                          _/_/  _/_/  _/    _/
(+43 664 / 951 83 72)    _/      _/  _/    _/


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
12