CVE-2021-22807
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 CWE-787: Out-of-bounds Write vulnerability exists that could cause arbitrary code execution when a malicious *.gd1 configuration file is loaded into the GUIcon tool. Affected Product: Eurotherm by Schneider Electric GUIcon Version 2.0 (Build 683.003) and prior
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 confidenceA CWE-787 out-of-bounds write vulnerability exists in Schneider Electric's GUIcon tool (versions 2.0 build 683.003 and prior). When the software parses a maliciously crafted .gd1 configuration file, it triggers an out-of-bounds memory write that can be exploited to achieve arbitrary code execution on the targeted system.
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.1/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.
-
Verify GUIcon installationSearch for GUIcon installation directories or check installed programs list for Schneider Electric GUIconAffected if GUIcon is installed on the system
-
Determine GUIcon versionLocate the GUIcon executable and check its file properties for version information, or run GUIcon with version check flag if availableAffected if The installed version is 2.0 with build number 683.003 or lower, or version information cannot be determined but GUIcon is present
-
Identify .gd1 file processingMonitor or inspect recent file access activities for .gd1 configuration files, or check GUIcon project/recent files list for .gd1 filesAffected if The system has recently loaded or currently hosts .gd1 configuration files
-
Check for untrusted file import capabilityReview GUIcon application settings or examine the file import mechanism to determine if .gd1 files from external or untrusted sources can be loadedAffected if GUIcon is configured to allow importing .gd1 files from locations outside trusted network segments
A system is affected if GUIcon version 2.0 build 683.003 or prior is installed and the software has the capability to load or has loaded .gd1 configuration files, regardless of source trustworthiness at the time of checking.
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 dataOrganizations should avoid loading any .gd1 configuration files from untrusted sources into GUIcon. Contact Schneider Electric for available patches or firmware updates. If using this software in production environments, implement network segmentation and restrict file import capabilities to trusted, verified configuration files only.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22807 — 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-2021-22807 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