CVE-2021-22755
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 inIGSS Definition (Def.exe) V15.0.0.21140 and prior that could result in disclosure of information or remote code execution due to lack of sanity checks on user-supplied data, when a malicious CGF file is imported to IGSS Definition.
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 confidenceAn out-of-bounds write vulnerability (CWE-787) exists in IGSS Definition (Def.exe) versions V15.0.0.21140 and prior. The vulnerability is triggered when importing a malicious CGF file due to insufficient validation of user-supplied data, allowing an attacker to write beyond allocated buffer boundaries and potentially achieve information disclosure or 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<= 15.0.0.21140CVSS 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.
-
Locate IGSS Definition executableSearch for Def.exe in typical installation directories such as C:\Program Files\Schneider Electric\IGSS\ or C:\Program Files (x86)\Schneider Electric\IGSS\, then right-click the file and select Properties to view the Version tabAffected if Def.exe is found with a version <= 15.0.0.21140
-
Check installed software versionOpen Windows Control Panel > Programs and Features, look for 'Schneider Electric Interactive Graphical Scada System' or 'IGSS' in the list and note the installed versionAffected if The installed version listed is 15.0.0.21140 or lower
-
Verify CGF import capabilityOpen IGSS Definition (Def.exe), navigate to the import or file open dialog, and confirm whether CGF file type is available as an import optionAffected if CGF file import functionality is present and accessible in the application
-
Identify active CGF workflowsCheck IGSS project directories for any .cgf files and review recent import activity logs if available in the IGSS systemAffected if CGF files are present in the environment or have been recently imported
A system is affected if IGSS Definition version is 15.0.0.21140 or lower AND the CGF file import feature is accessible or has been used in the environment.
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 the vendor patch when available. Until then, restrict CGF file imports to trusted sources only, and consider network segmentation to limit exposure of systems running IGSS Definition.
- Consultation6.0 h
- Implementation4.0 h
- Testing4.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 $4,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22755 — 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-22755 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