CVE-2012-2516
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 · uneditedAn ActiveX control in KeyHelp.ocx in KeyWorks KeyHelp Module (aka the HTML Help component), as used in GE Intelligent Platforms Proficy Historian 3.1, 3.5, 4.0, and 4.5; Proficy HMI/SCADA iFIX 5.0 and 5.1; Proficy Pulse 1.0; Proficy Batch Execution 5.6; SI7 I/O Driver 7.20 through 7.42; and other products, allows remote attackers to execute arbitrary commands via crafted input, related to a "command injection vulnerability."
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 confidenceA command injection vulnerability exists in the KeyHelp.ocx ActiveX control (KeyHelp Module/HTML Help component) used across multiple GE Intelligent Platforms products including Proficy Historian, Proficy HMI/SCADA iFIX, Proficy Pulse, Proficy Batch Execution, and SI7 I/O Driver. Remote attackers can execute arbitrary commands via crafted input to this ActiveX control.
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= 5.6= 3.1= 3.5= 4.0= 4.5= 5.0= 5.1= 1.0= 7.20= 7.42CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate the KeyHelp.ocx fileSearch the file system for KeyHelp.ocx. Typical paths include C:\Windows\System32\, C:\Windows\SysWOW64\, or installation directories of GE software (e.g., Proficy\Historian\, Proficy\iFIX\, Proficy\Batch\). Use: `dir /s /b C:\KeyHelp.ocx` or `Get-ChildItem -Path C:\ -Filter KeyHelp.ocx -Recurse -ErrorAction SilentlyContinue`Affected if The file KeyHelp.ocx exists on the system. If found, note its full path for version checking.
-
Determine KeyHelp.ocx file versionRight-click the found KeyHelp.ocx file, select Properties, then the Details tab. Alternatively, use PowerShell: `(Get-Item "<path to KeyHelp.ocx>").VersionInfo` or `filever.exe <path to KeyHelp.ocx>`Affected if The file version matches or falls within the vulnerable version range for the associated GE product. Compare against the affected product versions listed in the CVE.
-
Verify ActiveX control registrationOpen Windows Registry Editor and search for the KeyHelp control CLSID under HKLM\SOFTWARE\Microsoft\Code Store Database\Distribution Units\ or HKCR\CLSID\. Or run: `reg query "HKLM\SOFTWARE\Microsoft\Code Store Database\Distribution Units" /s /f KeyHelp`Affected if The KeyHelp.ocx ActiveX control is registered in the system registry, indicating it is available for use in web browsers or other containers.
-
Check installed GE product versionsUse Windows Programs and Features (appwiz.cpl) or PowerShell `Get-WmiObject Win32_Product` to list installed GE Intelligent Platforms software. Check versions of Proficy Historian, Proficy HMI/SCADA iFIX, Proficy Batch Execution, Proficy Pulse, and SI7 I/O Driver against the affected versions: Batch Execution 5.6, Historian 3.1/3.5/4.0/4.5, iFIX 5.0/5.1, Pulse 1.0, SI7 I/O Driver 7.20/7.42Affected if Any of the listed GE products are installed with versions matching or within the affected version ranges.
-
Check if ActiveX is enabled in Internet ExplorerFor systems with Internet Explorer, check if the KeyHelp control is allowed to run: Open IE, go to Internet Options > Security > Custom Level > ActiveX controls and plugins. Look for settings related to the KeyHelp control or verify via registry: `reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\Domains" /s /f KeyHelp`Affected if The KeyHelp ActiveX control is enabled or set to allow/run in browser security zones, particularly in the Internet or Intranet zones.
The environment is likely affected if KeyHelp.ocx is present AND matches the vulnerable version range AND the associated GE product is installed AND the ActiveX control is registered and enabled.
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 dataDeploy vendor patches from GE Intelligent Platforms for all affected products, or disable/remove the vulnerable KeyHelp.ocx ActiveX control if not required for operations. Implement network segmentation to limit exposure to untrusted networks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2516 — 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-2516 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