CVE-2006-5179: n/a vulnerability

CVE-2006-5179: Intoto iGateway VPN and iGateway SSL-VPN allow context-dependent attackers to cause a denial of service (CP...

Intoto iGateway VPN and iGateway SSL-VPN allow context-dependent attackers to cause a denial of service (CPU consumption) via parasitic public keys with large (1) "public exponent" or (2) "public modulus" values in X.509 certificates that require extra time to process when using RSA signature verification, a related issue to CVE-2006-2940.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 19:41 UTC (UTC+00:00)

Security readout for executives and security teams

This CVE describes a denial-of-service risk in Intoto iGateway VPN and iGateway SSL-VPN. An attacker who can present specially burdensome X.509 certificate data may cause excessive CPU use during RSA signature verification. The public record does not provide severity, affected versions, or a confirmed patch. Exposure is most likely in organizations still running legacy Intoto iGateway VPN or iGateway SSL-VPN systems, especially where certificate-processing paths are reachable by untrusted clients. The source bundle does not identify specific versions or deployment prerequisites. Treat this as a legacy VPN availability risk. The urgency depends on whether these products are still deployed and exposed. If present on internet-facing infrastructure, confirm support status and mitigation options promptly because the public record does not name a patch. Mitigation focus: Check vendor or successor guidance for fixed versions or supported migration paths.; Inventory any Intoto iGateway VPN or SSL-VPN deployments.; Restrict VPN certificate-authentication exposure to trusted networks where feasible..

Prepared: Jun 29, 2026, 10:06 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-5179 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: Oct 6, 2006, 00: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

1Source 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

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.