CVE-2012-1818
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 unspecified ActiveX control in Emerson DeltaV and DeltaV Workstations 9.3.1, 10.3.1, 11.3, and 11.3.1 and DeltaV ProEssentials Scientific Graph 5.0.0.6 allows remote attackers to overwrite arbitrary files via unknown 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 · moderate confidenceA vulnerability in an unspecified ActiveX control in Emerson DeltaV control systems (versions 9.3.1 through 11.3.1) and ProEssentials Scientific Graph 5.0.0.6 allows remote attackers to overwrite arbitrary files on the system. This ActiveX file overwrite vulnerability could allow an attacker to modify system configurations, replace binaries, or alter application files.
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= 9.3.1= 10.3.1= 11.3= 11.3.1= 5.0.0.6= 9.3.1= 10.3.1= 11.3= 11.3.1CVSS 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
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/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 DeltaV software is installedCheck Windows registry under HKLM\SOFTWARE\Emerson\DeltaV or look for DeltaV installation folders (typically in C:\Program Files\Emerson\DeltaV)Affected if DeltaV installation is found on the system
-
Determine the installed DeltaV versionCheck registry key HKLM\SOFTWARE\Emerson\DeltaV\CurrentVersion or inspect the version info of DeltaV executable files in the installation directoryAffected if Installed version matches 9.3.1, 10.3.1, 11.3, or 11.3.1
-
Verify ProEssentials Scientific Graph componentSearch for ProEssentials ActiveX control files (such as PEGraphOCX.dll) in the DeltaV installation directory or system32 folder, or check registry entries for ProEssentialsAffected if ProEssentials version 5.0.0.6 is present
-
Check ActiveX control enabled statusOpen Internet Explorer and navigate to Manage Add-ons (gear icon > Manage Add-ons), look for ProEssentials Graph Control or similar ActiveX control listed under 'ActiveX Controls'Affected if The ProEssentials ActiveX control is listed as enabled in the browser add-ons
-
Inspect browser security settings for ActiveXOpen Internet Explorer > Internet Options > Security > Custom Level, review settings under 'ActiveX controls and plug-ins' sectionAffected if ActiveX controls are set to enabled or prompt (not disabled) for the relevant zone
A user is affected if DeltaV versions 9.3.1, 10.3.1, 11.3, or 11.3.1 (or ProEssentials 5.0.0.6) are installed with the ProEssentials ActiveX control enabled in 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 available vendor patches from Emerson for DeltaV and ProEssentials components. If patches are unavailable, consider disabling the affected ActiveX control or implementing network segmentation to limit exposure to the control system network.
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1818 — 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-1818 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