CVE-2006-7140
First published: Wed Mar 07 2007(Updated: )
The libike library, as used by in.iked, elfsign, and kcfd in Sun Solaris 9 and 10, 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 libike from correctly verifying X.509 and other certificates that use PKCS #1, a similar issue to CVE-2006-4339.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Oracle Solaris SPARC | =10.0-hw2 | |
| Sun SunOS | =5.9 |
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.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2006-7140?
CVE-2006-7140 is considered a critical vulnerability due to its ability to allow remote attackers to forge signatures.
How do I fix CVE-2006-7140?
To resolve CVE-2006-7140, update the libike library to a version that addresses the RSA padding issue.
Which software is affected by CVE-2006-7140?
CVE-2006-7140 affects Sun Solaris 9 and 10 systems that utilize the libike library.
What types of attacks can exploit CVE-2006-7140?
CVE-2006-7140 can be exploited to perform signature forgery attacks against systems using vulnerable versions of the libike library.
Is CVE-2006-7140 specific to certain RSA keys?
Yes, CVE-2006-7140 specifically affects RSA keys that use an exponent of 3.
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/author
- agent/last-modified-date
- agent/severity
- agent/remedy
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/sun
- canonical/oracle solaris sparc
- version/oracle solaris sparc/10.0-hw2
- canonical/sun sunos
- version/sun sunos/5.9