CVE-2013-2785
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 buffer overflows in CimWebServer.exe in the WebView component in GE Intelligent Platforms Proficy HMI/SCADA - CIMPLICITY before 8.0 SIM 27, 8.1 before SIM 25, and 8.2 before SIM 19, and Proficy Process Systems with CIMPLICITY, allow remote attackers to execute arbitrary code via crafted data in packets to TCP port 10212, aka ZDI-CAN-1621 and ZDI-CAN-1624.
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 confidenceMultiple buffer overflow vulnerabilities in CimWebServer.exe (WebView component) in GE CIMPLICITY HMI/SCADA allow remote attackers to execute arbitrary code via crafted data sent to TCP port 10212. The vulnerabilities affect versions before 8.0 SIM 27, 8.1 before SIM 25, and 8.2 before SIM 19.
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.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
- 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.
-
Identify if GE CIMPLICITY is installedLook for CIMPLICITY installation directory, typically in Program Files\GE Intelligent Platforms\Proficy HMI/SCADA - Cimplicity, or check Windows Registry under HKLM\SOFTWARE\GE Intelligent Platforms\CIMPLICITY for the InstallDir valueAffected if GE CIMPLICITY is not installed on the system
-
Check the CIMPLICITY versionOpen CimExplorer.exe or go to Help > About in CIMPLICITY, or check the version info of the main executable. The version will show as 8.0, 8.1, or 8.2Affected if The installed version is 8.0, 8.1, or 8.2
-
Check the SIM (Service Information Module) levelIn CIMPLICITY, go to Help > About or check the SIM version displayed. For version 8.0, verify SIM 27 or higher; for 8.1, verify SIM 25 or higher; for 8.2, verify SIM 19 or higherAffected if The SIM level is below 27 for version 8.0, below 25 for version 8.1, or below 19 for version 8.2
-
Verify if WebView component is enabledCheck if CimWebServer.exe exists in the CIMPLICITY bin directory. In CIMPLICITY configuration, verify if WebView is enabled under Project > WebView SettingsAffected if CimWebServer.exe is present and WebView is enabled in the project configuration
-
Check if TCP port 10212 is listeningRun netstat -an | findstr 10212 or use PowerShell Get-NetTCPConnection -LocalPort 10212 to see if the CimWebServer is listening on port 10212Affected if Port 10212 is open and listening, indicating the vulnerable service is exposed
The system is affected if it runs GE CIMPLICITY versions 8.0 before SIM 27, 8.1 before SIM 25, or 8.2 before SIM 19, with WebView enabled and TCP port 10212 exposed.
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.
dbcve · scopedApply vendor-provided patches to reach the fixed SIM versions (8.0 SIM 27, 8.1 SIM 25, 8.2 SIM 19). As an interim control, restrict network access to TCP port 10212 and isolate the affected systems behind a DMZ until patching is complete.
CIMPLICITY 8.0 SIM 27+, 8.1 SIM 25+, or 8.2 SIM 19+
- Identify the currently installed CIMPLICITY version and SIM level via the project's properties or About dialog
- Navigate to the GE Intelligent Platforms support portal (support.ge-ip.com) and locate the CIMPLICITY product downloads section
- Download the appropriate Service Pack (SIM) update: for version 8.0 apply SIM 27 or later, for version 8.1 apply SIM 25 or later, for version 8.2 apply SIM 19 or later
- Ensure all CimWebServer services are stopped before applying the patch
- Apply the SIM update following the installation documentation provided with the patch
- Restart the CimWebServer service and verify the WebView component functions normally
- Confirm the patch was applied successfully by checking the version information in the About dialog
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,008.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2785 — 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-2013-2785 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