medium
4.3
CWE
310
Advisory Published
Updated

CVE-2006-4339

First published: Tue Sep 05 2006(Updated: )

OpenSSL before 0.9.7, 0.9.7 before 0.9.7k, and 0.9.8 before 0.9.8c, when using an RSA key with exponent 3, removes PKCS-1 padding before generating a hash, which allows remote attackers to forge a PKCS #1 v1.5 signature that is signed by that RSA key and prevents OpenSSL from correctly verifying X.509 and other certificates that use PKCS #1.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
OpenSSL libcrypto=0.9.5a-beta2
OpenSSL libcrypto=0.9.8b
OpenSSL libcrypto=0.9.6i
OpenSSL libcrypto=0.9.3
OpenSSL libcrypto=0.9.7c
OpenSSL libcrypto=0.9.5-beta1
OpenSSL libcrypto=0.9.6d
OpenSSL libcrypto=0.9.1c
OpenSSL libcrypto=0.9.6
OpenSSL libcrypto=0.9.7j
OpenSSL libcrypto=0.9.6a
OpenSSL libcrypto<=0.9.7
OpenSSL libcrypto=0.9.4
OpenSSL libcrypto=0.9.6a-beta2
OpenSSL libcrypto=0.9.5a
OpenSSL libcrypto=0.9.6f
OpenSSL libcrypto=0.9.6-beta3
OpenSSL libcrypto=0.9.6l
OpenSSL libcrypto=0.9.7g
OpenSSL libcrypto=0.9.6e
OpenSSL libcrypto=0.9.7d
OpenSSL libcrypto=0.9.6b
OpenSSL libcrypto=0.9.7e
OpenSSL libcrypto=0.9.7b
OpenSSL libcrypto=0.9.6a-beta1
OpenSSL libcrypto=0.9.6k
OpenSSL libcrypto=0.9.8a
OpenSSL libcrypto=0.9.6g
OpenSSL libcrypto=0.9.6-beta2
OpenSSL libcrypto=0.9.3a
OpenSSL libcrypto=0.9.6h
OpenSSL libcrypto=0.9.7i
OpenSSL libcrypto=0.9.7h
OpenSSL libcrypto=0.9.6j
OpenSSL libcrypto=0.9.8
OpenSSL libcrypto=0.9.7a
OpenSSL libcrypto=0.9.6c
OpenSSL libcrypto=0.9.6-beta1
OpenSSL libcrypto=0.9.6m
OpenSSL libcrypto=0.9.5-beta2
OpenSSL libcrypto=0.9.2b
OpenSSL libcrypto=0.9.5
OpenSSL libcrypto=0.9.5a-beta1
OpenSSL libcrypto=0.9.6a-beta3
OpenSSL libcrypto=0.9.7f

Remedy

http://secunia.com/advisories/21709

Remedy

http://www.debian.org/security/2006/dsa-1174

Remedy

http://www.openssl.org/news/secadv_20060905.txt

Remedy

http://www.securityfocus.com/bid/19849

Remedy

http://www.ubuntu.com/usn/usn-339-1

Remedy

http://www.us.debian.org/security/2006/dsa-1173

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2006-4339?

    CVE-2006-4339 is classified as a high-severity vulnerability due to its potential to allow remote signature forgery.

  • How do I fix CVE-2006-4339?

    To fix CVE-2006-4339, upgrade OpenSSL to versions 0.9.7k or later, or 0.9.8c or later.

  • What systems are affected by CVE-2006-4339?

    CVE-2006-4339 affects multiple versions of OpenSSL prior to 0.9.8c and includes versions such as 0.9.7 and earlier.

  • What type of attacks can exploit CVE-2006-4339?

    CVE-2006-4339 can be exploited to perform remote attacks that allow signature forgery, compromising data integrity.

  • Is there a workaround for CVE-2006-4339?

    There are no effective workarounds for CVE-2006-4339; the only recommended solution is to update to a secure version.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203