How severe is CVE-2006-7140?

CVE-2006-7140 has a CVSS 2.0 base score of 5.8, rated medium severity.

Is CVE-2006-7140 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (63rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2006-7140?

CVE-2006-7140 primarily affects Sun Solaris. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2006-7140?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2006-7140 published?

CVE-2006-7140 was published on 2007-03-07 and last updated on 2026-06-16.

CVE-2006-7140

CVE-2006-7140 is a medium-severity vulnerability in Sun Solaris with a CVSS 2.0 base score of 5.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 2.0 base score 5.8)
EPSS exploit prediction: 1% (63rd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Sun Solaris
Published: 2007-03-07
Last modified: 2026-06-16

Description

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.

Frequently asked questions

What is CVE-2006-7140?: 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.
How severe is CVE-2006-7140?: CVE-2006-7140 has a CVSS 2.0 base score of 5.8, rated medium severity.
Is CVE-2006-7140 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (63rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2006-7140?: CVE-2006-7140 primarily affects Sun Solaris. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2006-7140?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2006-7140 published?: CVE-2006-7140 was published on 2007-03-07 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:o:sun:solaris:10.0:hw2:*:*:*:*:*:*
cpe:2.3:o:sun:sunos:5.9:*:*:*:*:*:*:*

More vulnerabilities in Sun Solaris

CVE-2009-2296 — Critical (CVSS 10.0): The NFSv4 server kernel module in Sun Solaris 10, and OpenSolaris before snv_119, does not properly implement the…
CVE-2008-3870 — Critical (CVSS 10.0): Integer overflow in sadmind in Sun Solaris 8 and 9 allows remote attackers to execute arbitrary code via a crafted RPC…
CVE-2008-3869 — Critical (CVSS 10.0): Heap-based buffer overflow in sadmind in Sun Solaris 8 and 9 allows remote attackers to execute arbitrary code via a…
CVE-2008-5010 — Critical (CVSS 10.0): in.dhcpd in the DHCP implementation in Sun Solaris 8 through 10, and OpenSolaris before snv_103, allows remote…
CVE-2008-4556 — Critical (CVSS 10.0): Stack-based buffer overflow in the adm_build_path function in sadmind in Sun Solstice AdminSuite on Solaris 8 and 9…
CVE-2007-3093 — Critical (CVSS 10.0): Unspecified vulnerability in the logging mechanism in Solaris Management Console (SMC) on Sun Solaris 8 through 10…

All CVEs affecting Sun Solaris →