CVE-2006-4790

Description

verify.c in GnuTLS before 1.4.4, when using an RSA key with exponent 3, does not properly handle excess data in the digestAlgorithm.parameters field when generating a hash, which allows remote attackers to forge a PKCS #1 v1.5 signature that is signed by that RSA key and prevents GnuTLS from correctly verifying X.509 and other certificates that use PKCS, a variant of CVE-2006-4339.

5.0

CVSS

Severity: Medium

CVSS 2.0 •

EPSS 3.08% Top 15%

Vendor Advisory novell.com Vendor Advisory mandriva.com Vendor Advisory redhat.com Vendor Advisory sun.com Vendor Advisory gentoo.org Vendor Advisory novell.com Vendor Advisory debian.org Vendor Advisory sun.com Vendor Advisory ubuntu.com

Affected: n/a n/a

References

Link	Tags
http://secunia.com/advisories/25762	third party advisory
http://secunia.com/advisories/22992	third party advisory
http://secunia.com/advisories/21937	third party advisory
http://secunia.com/advisories/22049	third party advisory
http://securitytracker.com/id?1016844	vdb entry
http://www.vupen.com/english/advisories/2006/3899	vdb entry
http://www.securityfocus.com/bid/20027	vdb entry
http://www.novell.com/linux/security/advisories/2006_23_sr.html	vendor advisory
http://www.mandriva.com/security/advisories?name=MDKSA-2006:166	vendor advisory
http://www.redhat.com/support/errata/RHSA-2006-0680.html	patch vendor advisory
http://www.gnu.org/software/gnutls/security.html	patch
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A9937	vdb entry signature
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102970-1	vendor advisory
http://www.vupen.com/english/advisories/2006/3635	vdb entry
http://secunia.com/advisories/21942	third party advisory
http://lists.gnupg.org/pipermail/gnutls-dev/2006-September/001205.html	mailing list
http://secunia.com/advisories/22080	third party advisory
http://security.gentoo.org/glsa/glsa-200609-15.xml	vendor advisory
http://www.novell.com/linux/security/advisories/2007_10_ibmjava.html	vendor advisory
http://www.debian.org/security/2006/dsa-1182	vendor advisory
http://support.avaya.com/elmodocs2/security/ASA-2006-250.htm
https://exchange.xforce.ibmcloud.com/vulnerabilities/28953	vdb entry
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102648-1	vendor advisory
http://secunia.com/advisories/21973	third party advisory
http://secunia.com/advisories/22226	third party advisory
http://secunia.com/advisories/22084	third party advisory
http://lists.gnupg.org/pipermail/gnutls-dev/2006-September/001212.html	mailing list
http://www.ubuntu.com/usn/usn-348-1	vendor advisory
http://www.vupen.com/english/advisories/2007/2289	vdb entry
http://secunia.com/advisories/22097	third party advisory

Frequently Asked Questions

What is the severity of CVE-2006-4790?: CVE-2006-4790 has been scored as a medium severity vulnerability.
How to fix CVE-2006-4790?: To fix CVE-2006-4790, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2006-4790 being actively exploited in the wild?: It is possible that CVE-2006-4790 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~3% probability that this vulnerability will be exploited by malicious actors in the next 30 days.