CVE-2018-7815
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 · uneditedA Type Confusion (CWE-843) vulnerability exists in Eurotherm by Schneider Electric GUIcon V2.0 (Gold Build 683.0) on c3core.dll which could cause remote code to be executed when parsing a GD1 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 confidenceA type confusion vulnerability in c3core.dll of Eurotherm by Schneider Electric GUIcon V2.0 (Gold Build 683.0) allows remote code execution when parsing maliciously crafted GD1 files. The vulnerability stems from improper type validation during file parsing, which can be exploited to corrupt memory and execute arbitrary code.
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= 2.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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 GUIcon installationCheck if Eurotherm by Schneider Electric GUIcon software is installed on the system by looking in Program Files or Program Files (x86) for a folder named 'GUIcon' or similar Eurotherm/Schneider Electric GUI applications.Affected if GUIcon version 2.0 is installed on the system.
-
Identify GUIcon versionRight-click the GUIcon executable or its shortcut, select Properties, and check the File Version details. Alternatively, open GUIcon and navigate to Help > About to view the version information.Affected if The installed version is exactly 2.0 (Gold Build 683.0).
-
Locate c3core.dllSearch the GUIcon installation directory for the presence of c3core.dll file. Check the file properties to verify it is the component associated with this vulnerability.Affected if c3core.dll exists in the GUIcon installation folder.
-
Verify GD1 file handling is enabledCheck if the GUIcon application has functionality to import, open, or parse GD1 files. Look for file import options or GD1-related menu items within the application interface.Affected if GD1 file import or parsing features are accessible or frequently used.
-
Inspect for GD1 files on systemSearch the system for .gd1 file extensions, particularly in shared folders, downloads, or project directories that may contain imported Eurotherm configuration files.Affected if Untrusted or unknown GD1 files are present on the system and could be loaded by GUIcon.
A system is affected if Schneider Electric GUIcon version 2.0 (Gold Build 683.0) is installed and the application is used to parse GD1 files.
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 vendor-supplied patches for GUIcon V2.0; if unavailable, isolate affected systems on a restricted network segment and implement strict file import controls to prevent loading untrusted GD1 files.
- Consultation8.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,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7815 — 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-7815 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