CVE-2011-4870
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceBuffer overflow vulnerability in three Wonderware InBatch ActiveX controls (GUIControls, BatchObjSrv, BatchSecCtrl) allows remote attackers to execute arbitrary code by supplying a long string in property values. Affected versions include InBatch 9.0, 9.0 SP1, 8.1 SP1, 9.0 SP2, and 9.5 Server and Runtime Clients.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 8.1= 9.0= 9.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Wonderware InBatch is installedCheck for InBatch installation directories (commonly in Program Files/Wonderware) or look for Wonderware InBatch in Add/Remove ProgramsAffected if If Wonderware InBatch software is found on the system
-
Determine the installed InBatch versionLocate version information in the InBatch installation directory, typically in version.dll or a version file within the installation folder, or check the program properties in Add/Remove ProgramsAffected if If the version is 8.1, 9.0, 9.0 SP1, 9.0 SP2, or 9.5 (any of the affected versions listed in the CVE)
-
Verify presence of vulnerable ActiveX controlsSearch for the affected DLLs (guicontrols.dll, batchobjsrv.dll, batchs.ctrl.dll or similar) in the InBatch installation directory, or check Windows registry under HKLM\SOFTWARE\Classes\CLSID for entries containing GUIControls, BatchObjSrv, or BatchSecCtrlAffected if If any of these three ActiveX controls (GUIControls, BatchObjSrv, BatchSecCtrl) are present on the system
System is likely affected if Wonderware InBatch version 8.1, 9.0, or 9.5 is installed and any of the three vulnerable ActiveX controls (GUIControls, BatchObjSrv, BatchSecCtrl) are present and registered on the system.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor patches when available; alternatively, disable the affected ActiveX controls or implement network segmentation to limit exposure to untrusted networks.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4870 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-4870 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data