dbcve.org
Wonderware InbatchApplication · Invensys

CVE-2011-3141

HIGH · 9.3 CVSS v2.0 Published 2011-08-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Buffer overflow in the InBatch BatchField ActiveX control for Invensys Wonderware InBatch 8.1 SP1, 9.0, and 9.0 SP1 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via unspecified vectors.

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 · high confidence

A buffer overflow vulnerability exists in the InBatch BatchField ActiveX control used by Invensys Wonderware InBatch versions 8.1 SP1, 9.0, and 9.0 SP1. The overflow can be triggered remotely by unspecified vectors, leading to denial of service (crash) and potential arbitrary code execution.

MitigationDisable or remove the vulnerable InBatch BatchField ActiveX control, apply any available vendor patches, and implement network segmentation to restrict exposure to untrusted networks.

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
Wonderware InbatchApplication
Affected:= 8.1= 9.0

CVSS 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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify InBatch installation and version
    Check the Windows registry for the Wonderware InBatch installation under HKLM\SOFTWARE\Wonderware\InBatch or look for the InBatch application in Add/Remove Programs. The version will be listed in the registry or program properties.
    Affected if The installed version is 8.1 SP1, 9.0, or 9.0 SP1.
  2. Locate the BatchField ActiveX control file
    Search for the ActiveX control file (typically named BatchField.ocx or similar) in the Wonderware InBatch installation directory, commonly found in the bin or system32 folder under the Wonderware installation path.
    Affected if The BatchField.ocx file exists and matches the affected InBatch version.
  3. Verify ActiveX control registration
    Open Command Prompt and run 'regsvr32 /u [path]\BatchField.ocx' to check if the control is registered, or check the registry under HKLM\SOFTWARE\Classes\CLSID for entries containing 'BatchField' or the InBatch BatchField component.
    Affected if The BatchField ActiveX control is registered on the system.
  4. Check if ActiveX controls are enabled
    In Internet Explorer settings (if used), verify whether ActiveX controls and scripts are allowed to run, or check the Windows Internet Settings under Tools > Internet Options > Security > Custom Level for ActiveX settings.
    Affected if ActiveX controls are enabled and the vulnerable control is present.
  5. Assess network exposure
    Review firewall rules and network segmentation to determine if the system running InBatch is accessible from untrusted networks, as the exploit is triggered remotely via unspecified vectors.
    Affected if The InBatch server is directly accessible from untrusted or external networks.

A user is affected if Wonderware InBatch version 8.1 SP1, 9.0, or 9.0 SP1 is installed with the BatchField ActiveX control present and registered on a system accessible to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable or remove the vulnerable InBatch BatchField ActiveX control, apply any available vendor patches, and implement network segmentation to restrict exposure to untrusted networks.

Recommended fix Moderate confidence

Contact vendor for latest supported InBatch version

  1. Contact Schneider Electric (current owner of Wonderware/Aveva) to request the specific security patch for CVE-2011-3141
  2. Request patch availability for Wonderware InBatch versions 8.1 SP1, 9.0, and 9.0 SP1
  3. If patches are unavailable, evaluate upgrading to a later supported InBatch version recommended by the vendor
  4. As a compensating control, disable the BatchField ActiveX control in Internet Explorer by adding the ActiveX control's CLSID to the Internet Explorer kill bit list
  5. Restrict network access to systems running InBatch to minimize attack surface
Caveat Verify application compatibility with any version upgrade in a test environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wonderware Inbatch Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA4.0 h
40.0 hours of engineering $6,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,008.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-3141 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-3141 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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