CVE-2014-0751
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 CIMPLICITY Web-based access component, CimWebServer, does not check the location of shell files being loaded into the system. By modifying the source location, an attacker could send shell code to the CimWebServer which would deploy the nefarious files as part of any SCADA project. This could allow the attacker to execute arbitrary code.
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 confidenceCIMPLICITY CimWebServer component fails to validate the location of shell files being loaded, allowing path traversal attacks where attackers can specify arbitrary file paths to deploy malicious shell code to the SCADA project directory and achieve remote code execution.
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.2= 4.01= 7.5= 8.0= 8.1= 8.2all 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
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/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.
-
Verify if CimWebServer component is installed and runningCheck Windows services for 'CimWebServer' service or review CIMPLICITY installation for the 'CimWebServer' directory under the CIMPLICITY installation path (typically C:\Program Files\GE\Cimplicity\CimWebServer or similar)Affected if CimWebServer service exists and is running, or the CimWebServer directory is present on the system
-
Determine the CIMPLICITY version installedOpen Windows Registry under HKLM\SOFTWARE\GE\Intelligent Platforms\Proficy\Cimplicity\CurrentVersion or check the Cimplicity version displayed in the Cimplicity Workbench > Help > About. Also check Add/Remove Programs for installed CIMPLICITY versions.Affected if Installed version matches 4.01, 7.5, 8.0, 8.1, 8.2 or is older than or equal to 8.2, or if using 'Ge Intelligent Platforms Proficy Process Systems With Cimplicity' (all versions)
-
Confirm network accessibility of the CimWebServer interfaceCheck if TCP ports 80 or 443 (or configured web server ports) are open and listening on the CimWebServer host. Use 'netstat -an | findstr :80' or a port scanner to verify. Also check firewall rules for inbound允许CimWebServer端口.Affected if CimWebServer HTTP/HTTPS ports are open and accessible from network positions where the SCADA system should be isolated
-
Inspect SCADA project directory for unauthorized filesReview the CIMPLICITY project directory (typically found in the project's folder or under C:\CimProjects or similar) for unexpected .exe, .bat, .cmd, .dll, or script files that were not deployed by legitimate administrators. Compare against known-good baseline if available.Affected if Unknown executable or script files are present in the project directory, especially in locations accessible via the web server's deployed path
The environment is affected if CimWebServer is enabled and the installed CIMPLICITY version is 4.01, 7.5, 8.0, 8.1, <=8.2, or any version of 'Process Systems With Cimplicity', combined with network accessibility of the web interface.
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 dataDisable CimWebServer if not required, apply vendor patches when available, and implement network segmentation to restrict access to the web interface.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.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,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0751 — 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-0751 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