Skip to content
Fencer Intel
critical 10.0

CVE-2010-4597 in the critical feed json

Stack-based buffer overflow in the save method in the IntegraXor.Project ActiveX control in igcomm.dll in Ecava IntegraXor Human-Machine In…

published 2010-12-23 15 y ago modified 2026-06-16 4 mo ago also EUVD-2010-4563

cvss
10.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
18.8%
EPSS 18.8% chance of exploitation in 30 days, percentile 97%
public exploits
1
Exploit-DB

Summary

Stack-based buffer overflow in the save method in the IntegraXor.Project ActiveX control in igcomm.dll in Ecava IntegraXor Human-Machine Interface (HMI) before 3.5.3900.10 allows remote attackers to execute arbitrary code via a long string in the second argument.

Patch / fix

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-10-322-01 updated cvss 10.0

Ecava IntegraXor Buffer Overflow

  • Ecava Easy Connect (EC150) Ecava Modbus RTU – TCP Gateway (MB100) Ecava Serial Ethernet Server (SS100) Ecava WebSCADA (WS100) Ecava WebSCADA (WS200)
    affected: mitigation “For more information, customers can contact Ecava support at (mailto:support@integraxor.com).”

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Timeline

  1. First public exploit (EDB-15767)
  2. Published

Exploit prediction

18.82% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-15767 Ecava IntegraXor Remote - ActiveX Buffer Overflow (PoC) dos, 2010-12-18
  • securityfocus.com http://www.securityfocus.com/bid/45487 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.