From secunia security advisor at $URL.
1) An error within OpenSSL's internal certificate verification can lead to OpenSSL accepting CRL (Certificate Revocation Lists) with a "nextUpdate" field set to a date in the past.
2) An error within the implementation of ephemeral ECDH ciphersuites can be exploited to crash a vulnerable server by sending handshake messages within an invalid order.
Successful exploitation of this vulnerability requires that the server enabled and supports the ECDH ciphersuites.
The vulnerabilities are reported in versions 1.0.0 through 1.0.0d.
Update to version 1.0.0e.
1.0.0e now in the tree
Arch teams, please, stabilize openssl-1.0.0e. TIA.
tested many rdeps
+ 07 Sep 2011; Tony Vroon <firstname.lastname@example.org> openssl-1.0.0e.ebuild:
+ Marked stable on AMD64 based on arch testing by Agostino "ago" Sarubbo in
+ security bug #382069.
Archtested on x86: Everything fine
(In reply to comment #5)
> Archtested on x86: Everything fine
Looks ok also for me on x86
Stable for HPPA.
arm/x86 stable, thnks JD and Agostino
Thanks, everyone. Added to existing GLSA request.
The ephemeral ECDH ciphersuite functionality in OpenSSL 0.9.8 through 0.9.8s
and 1.0.x before 1.0.0e does not ensure thread safety during processing of
handshake messages, which allows remote attackers to cause a denial of
service (application crash) via out-of-order messages that violate the TLS
crypto/x509/x509_vfy.c in OpenSSL 1.0.x before 1.0.0e does not initialize
certain structure members, which makes it easier for remote attackers to
bypass CRL validation by using a nextUpdate value corresponding to a time in
This issue was resolved and addressed in
201110-01 at http://security.gentoo.org/glsa/glsa-201110-01.xml
by GLSA coordinator Tobias Heinlein (keytoaster).