CVE-2018-15362
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 · uneditedXXE in GE Proficy Cimplicity GDS versions 9.0 R2, 9.5, 10.0
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 confidenceXML External Entity (XXE) injection vulnerability in GE Proficy Cimplicity GDS allows attackers to inject malicious XML entities to read internal files, perform Server-Side Request Forgery (SSRF), or cause Denial of Service. The 9.1 CVSS score indicates remote, unauthenticated exploitation with high impact to confidentiality and availability.
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.0_r2= 9.5= 10.0CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
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.
-
Confirm GE Proficy Cimplicity is installedCheck for Cimplicity installation directory (typically C:\Program Files\GE Fanuc\Proficy\Proficy Cimplicity or similar) or look for Cimplicity services in Windows ServicesAffected if Cimplicity software is present on the system
-
Identify Cimplicity GDS component versionCheck version information in the GDS component: look for version file in the GDS installation folder, or right-click the GDS executable and view Properties > Details for version numberAffected if Version is 9.0_r2, 9.5, or 10.0 exactly as listed in affected versions
-
Verify GDS service is runningOpen Windows Services and look for 'Cimplicity GDS' or 'GE Proficy Cimplicity GDS' service, or check if GDS process is active in Task ManagerAffected if GDS service is running and accepting XML input
-
Check XML parser configurationInspect GDS configuration files (typically in the GDS config folder) for XML parser settings related to external entity processing, or check if the XML parser has DTD processing enabledAffected if External entity processing is enabled in the XML parser configuration
You are affected if GE Proficy Cimplicity with GDS component versions 9.0_r2, 9.5, or 10.0 is installed and the GDS service is running with XML external entity processing 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 dataDisable external entity processing in XML parsers within the GDS component, apply vendor patches if available, and restrict network access to the GDS service as a compensating control.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15362 — 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-2018-15362 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