CVE-2011-4870 json
Multiple buffer overflows in the (1) GUIControls, (2) BatchObjSrv, and (3) BatchSecCtrl ActiveX controls in Invensys Wonderware InBatch 9.0…
published 2012-01-08 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4787
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
Multiple buffer overflows in the (1) GUIControls, (2) BatchObjSrv, and (3) BatchSecCtrl ActiveX controls in Invensys Wonderware InBatch 9.0 and 9.0 SP1, and InBatch 8.1 SP1, 9.0 SP2, and 9.5 Server and Runtime Clients, allow remote attackers to execute arbitrary code via a long string in a property value, a different issue than CVE-2011-3141.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-11-332-01A updated cvss 6.8
Wonderware InBatch ActiveX Vulnerabilities
-
Invensys Wonderware InBatch 9.0, 9.0_SP1. Invensys Wonderware InBatch Server and Runtime Clients 8.1, SP1, 9.0, SP2, 9.5affected: mitigation “To access information related to Invensys security updates, customers can logon to the Cyber Security Updates website and the GCS Foxboro Wonderware Security Releases webpage.”
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
Exploit prediction
2.39% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
us-cert.gov
/control_systems/pdf/ICSA-11-332-01A.pdf
us-government-resource
-
securityfocus.com
/bid/51129
vdb-entry
Sources
- CVE List CVE-2011-4870
- NVD CVE-2011-4870
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.