CVE-2014-2355
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 · uneditedThe (1) CimView and (2) CimEdit components in GE Proficy HMI/SCADA-CIMPLICITY 8.2 and earlier allow remote attackers to gain privileges via a crafted CIMPLICITY screen (aka .CIM) file.
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 confidenceThis vulnerability in GE Proficy HMI/SCADA-CIMPLICITY 8.2 and earlier allows privilege escalation through malicious .CIM screen files. The CimView and CimEdit components fail to properly validate crafted CIMPLICITY screen files, enabling remote attackers to gain elevated privileges when a user opens the malicious file.
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.2CVSS 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
- Local
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/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.
-
Verify GE Proficy CIMPLICITY is installedCheck the Windows registry or common installation directories for GE Proficy CIMPLICITY components such as CimView.exe or CimEdit.exeAffected if Either CimView or CimEdit executable files are present on the system
-
Determine the installed CIMPLICITY versionUse the application's About dialog, check the registry, or query the installed software in Windows Control Panel for the exact version numberAffected if The installed version is 8.2 or any version lower than 8.2
-
Confirm CIM file association with vulnerable componentsCheck Windows file associations to verify if .CIM files are linked to CimView or CimEdit executablesAffected if CIM files are configured to open with CimView or CimEdit and the version is 8.2 or lower
-
Identify active user permissionsReview the user accounts that typically open CIM files in the CIMPLICITY environmentAffected if Users with standard privileges open .CIM files in an environment running version 8.2 or lower
The environment is affected if GE Proficy CIMPLICITY version 8.2 or lower is installed and .CIM screen files are handled by the CimView or CimEdit components.
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 dataUpgrade to a patched version of GE Proficy CIMPLICITY. Until then, implement controls to prevent untrusted .CIM files from being opened by CIMPLICITY applications, and isolate affected systems via network segmentation.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA5.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2355 — 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-2014-2355 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