OpenSSL Security Advisory [5th September 2006]
RSA Signature Forgery (CVE-2006-4339)
Daniel Bleichenbacher recently described an attack on PKCS #1 v1.5
signatures. If an RSA key with exponent 3 is used it may be possible
to forge a PKCS #1 v1.5 signature signed by that key. Implementations
may incorrectly verify the certificate if they are not checking for
excess data in the RSA exponentiation result of the signature.
Since there are CAs using exponent 3 in wide use, and PKCS #1 v1.5 is
used in X.509 certificates, all software that uses OpenSSL to verify
X.509 certificates is potentially vulnerable, as well as any other use
of PKCS #1 v1.5. This includes software that uses OpenSSL for SSL or
OpenSSL versions up to 0.9.7j and 0.9.8b are affected.
The Common Vulnerabilities and Exposures project (cve.mitre.org) has
assigned the name CAN-2006-4339 to this issue.
There are multiple ways to avoid this vulnerability. Any one of the
following measures is sufficient.
1. Upgrade the OpenSSL server software.
The vulnerability is resolved in the following versions of OpenSSL:
- in the 0.9.7 branch, version 0.9.7k (or later);
- in the 0.9.8 branch, version 0.9.8c (or later).
OpenSSL 0.9.8c and OpenSSL 0.9.7k are available for download via
HTTP and FTP from the following master locations (you can find the
various FTP mirrors under http://www.openssl.org/source/mirror.html):
The distribution file names are:
MD5 checksum: 78454bec556bcb4c45129428a766c886
SHA1 checksum: d0798e5c7c4509d96224136198fa44f7f90e001d
MD5 checksum: be6bba1d67b26eabb48cf1774925416f
SHA1 checksum: 90056b8f5e518edc9f74f66784fbdcfd9b784dd2
The checksums were calculated using the following commands:
openssl md5 openssl-0.9*.tar.gz
openssl sha1 openssl-0.9*.tar.gz
2. If this version upgrade is not an option at the present time,
alternatively the following patch may be applied to the OpenSSL
source code to resolve the problem. The patch is compatible with
the 0.9.7, 0.9.8, and 0.9.9 branches of OpenSSL.
Whether you choose to upgrade to a new version or to apply the patch,
make sure to recompile any applications statically linked to OpenSSL
The OpenSSL team thank Philip Mackenzie, Marius Schilder, Jason Waddle
and Ben Laurie, of Google Security, who successfully forged various
certificates, showing OpenSSL was vulnerable, and provided the patch
to fix the problems.
URL for this Security Advisory:
base-system please advise.
both versions now in portage
Arches please test and mark stable.
Marked ppc stable.
amd64 stable, w00t w00t
openssl-0.9.7k stable on sparc.
0.9.8c stable on ppc64
x86 stable. ^.^
removing x86 as I forgot.
*** Bug 146557 has been marked as a duplicate of this bug. ***
since the update I can't use https/sasl anymore. You can read the full story here: http://forums.gentoo.org/viewtopic-t-495860.html
I reemerged dev-libs/openssl-0.9.7j with above patch applied and now it works again.
I hope this just happens on my box. :-)
No, it doesn't. I got hosed, too. Still checking the details :/
> No, it doesn't. I got hosed, too. Still checking the details :/
https works nicefully here (x86)
NB HPPA: we're just waiting for you before issuing the GLSA. Something wrong ?
Yeah, blooper with qca-tls. I needed 1.0-r3 (~x86, stable wouldn't compile).
0.9.7k hppa stable.
i'm getting some different answers from a lot of folks, so maybe someone here could advise me. If i update 0.9.7i and update to 0.9.7j, would i need to revdep-rebuild everything or are they binary compatible ?
all 0.9.6 versions are ABI compat with each other
all 0.9.7 versions are ABI compat with each other
all 0.9.8 versions are ABI compat with each other
*** Bug 146421 has been marked as a duplicate of this bug. ***