Skip to content
Fencer Intel
critical 9.3

CVE-2011-2089 in the critical feed json

Stack-based buffer overflow in the SetActiveXGUID method in the VersionInfo ActiveX control in GenVersion.dll 8.0.138.0 in the WebHMI subsy…

published 2011-05-13 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-2081

cvss
9.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
38.3%
EPSS 38.3% chance of exploitation in 30 days, percentile 98%
public exploits
3
Metasploit, Exploit-DB

Summary

Stack-based buffer overflow in the SetActiveXGUID method in the VersionInfo ActiveX control in GenVersion.dll 8.0.138.0 in the WebHMI subsystem in ICONICS BizViz 9.x before 9.22 and GENESIS32 9.x before 9.22 allows remote attackers to execute arbitrary code via a long string in the argument. NOTE: some of these details are obtained from third party information.

Vendor advisories

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

cisa ICSA-11-131-01 updated cvss 9.8

ICONICS GENESIS32 and BizViz ActiveX Stack Overflow

  • ICONICS BizViz >=9, <=9.21 ICONICS GENESIS32 >=9, <=9.21
    affected: mitigation “ICONICS has updated their “Whitepaper on Security Vulnerabilities” (http://iconics.com/certs) to include details of this vulnerability.”

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-17240)
  2. Published

Exploit prediction

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

Exploits and checks

CVSS scores

assigned by version score vector
NVD 2.0 9.3 AV:N/AC:M/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.