CVE-2012-1801
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 stack-based buffer overflows in (1) COM and (2) ActiveX controls in ABB WebWare Server, WebWare SDK, Interlink Module, S4 OPC Server, QuickTeach, RobotStudio S4, and RobotStudio Lite allow remote attackers to execute arbitrary code via crafted input data.
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 confidenceMultiple stack-based buffer overflow vulnerabilities exist in ABB's COM and ActiveX controls across WebWare Server, WebWare SDK, Interlink Module, S4 OPC Server, QuickTeach, RobotStudio S4, and RobotStudio Lite. Remote attackers can execute arbitrary code by sending crafted input data to these vulnerable controls.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Adjacent
- Complexity
- Low
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:A/AC:L/Au:S/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed ABB productsCheck for presence of ABB software by looking in Program Files for folders named ABB, or search for executable files associated with the affected products: Interlink Module, QuickTeach, RobotStudio, S4 OPC Server, WebWare SDK, WebWare Server. Use 'Get-ItemProperty' or 'dir' to search installation directories.Affected if Any of the seven affected ABB products (Interlink Module, QuickTeach, RobotStudio Lite, RobotStudio S4, S4 OPC Server, WebWare SDK, WebWare Server) are installed on the system
-
Locate COM and ActiveX controlsCheck Windows Registry for registered COM components from ABB. Look in HKLM\SOFTWARE\Classes for CLSIDs with vendor 'ABB' or product-related identifiers. Use 'reg query' commands to search for ABB entries in the registry.Affected if COM or ActiveX controls from the affected ABB products are registered on the system (the vulnerability exists in these controls regardless of version)
-
Check for vulnerable DLL filesSearch for DLL files associated with the affected products in installation directories. Common ABB control DLLs may be named with product identifiers like 'ABB', 'WebWare', 'Interlink', 'RobotStudio', or 'QuickTeach'. Use 'Get-ChildItem' or 'dir' to search.Affected if DLL files implementing the vulnerable COM/ActiveX controls are present on the system
-
Verify network exposureCheck if the system is accessible over network on ports used by the affected products (WebWare Server typically uses HTTP ports, S4 OPC Server uses OPC ports). Use 'netstat -an' to list listening ports and correlate with running ABB services.Affected if The system with ABB products is network-accessible and the vulnerable controls can receive crafted input from remote attackers
A user is affected if any of the seven ABB products (Interlink Module, QuickTeach, RobotStudio Lite, RobotStudio S4, S4 OPC Server, WebWare SDK, WebWare Server) are installed, as all versions contain the vulnerable COM/ActiveX controls.
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 all available vendor patches for the affected ABB products. Until patches are available, restrict network exposure of vulnerable controls and disable ActiveX controls in untrusted contexts.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1801 — 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-2012-1801 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