Progea Movicon / PowerHMI 11.2.1085 and earlier allows remote attackers to cause a denial of service (memory corruption and crash) and poss…

published 2011-09-16 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-3462

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

Progea Movicon / PowerHMI 11.2.1085 and earlier allows remote attackers to cause a denial of service (memory corruption and crash) and possibly execute arbitrary code via an EIDP packet with a large size field, which writes a zero byte to an arbitrary memory location.

Vendor advisories

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

cisa ICSA-11-294-01 updated 2025-06-09 cvss 10.0

Progea Movicon Power HMI Vulnerabilities

Progea Movicon <=11.2.1085.3 Progea Movicon PowerHMI <=11.2.1085
affected: mitigation

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

2011-09-14 First public exploit (EDB-17842)
2011-09-16 Published

Exploit prediction

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

Exploits and checks

EDB-17842 progea movicon / powerhmi 11.2.1085 - Multiple Vulnerabilities dos, 2011-09-14
aluigi.altervista.org http://aluigi.altervista.org/adv/movicon_3-adv.txt 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

aluigi.altervista.org /adv/movicon_3-adv.txt
exploit
exchange.xforce.ibmcloud.com /vulnerabilities/69789
vdb-entry
us-cert.gov /control_systems/pdf/ICS-ALERT-11-256-01.pdf
us-government-resource

Sources

CVE List CVE-2011-3499
NVD CVE-2011-3499

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.

Summary