CVE-2006-7140: n/a vulnerability

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 wi...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 20:50 UTC (UTC+00:00)

Security readout for executives and security teams

This issue affects Sun Solaris 9 and 10 systems using libike with RSA keys that use exponent 3. The certificate verification logic may accept forged PKCS #1 v1.5 signatures. Business risk depends on whether legacy Solaris hosts and affected keys still exist in the environment. Exposure is most likely on legacy Sun Solaris 9 or 10 systems running components that depend on libike and use RSA exponent 3 certificates or keys. The provided data does not identify other affected products or versions. Treat this as a legacy-platform exposure review. It may be urgent if Solaris 9 or 10 systems still support VPN, signing, certificate validation, or trust-anchor workflows. If those systems are retired or isolated, priority is lower. Mitigation focus: Check Sun Alert 102722 for vendor-confirmed patches or operational guidance.; Inventory Solaris 9 and 10 hosts using in.iked, elfsign, kcfd, or libike.; Identify RSA exponent 3 certificates or keys used by affected components..

Prepared: Jun 29, 2026, 07:07 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2006-7140 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Mar 7, 2007, 20:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
oval:org.mitre.oval:def:1648CVE reference · vdb-entry, signature

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.