CVE-2021-22758
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-824: Access of uninitialized pointer vulnerability exists inIGSS Definition (Def.exe) V15.0.0.21140 and prior that could result in loss of data or remote code execution due to lack validation of user-supplied input 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 · moderate confidenceA CWE-824 (Access of uninitialized pointer) vulnerability exists in IGSS Definition (Def.exe) versions prior to V15.0.0.21140. The vulnerability is triggered when importing a malicious CGF file, due to the application failing to validate user-supplied input data before using it as a pointer. This can lead to memory corruption enabling remote code execution or data loss.
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.
-
Verify IGSS Definition is installedLocate the Def.exe executable - typically found in C:\Program Files\Schneider Electric\IGSS\ or C:\Program Files (x86)\Schneider Electric\IGSS\. Use File Explorer or PowerShell: Get-ChildItem -Path 'C:\Program Files','C:\Program Files (x86)' -Recurse -Filter 'Def.exe' -ErrorAction SilentlyContinueAffected if Def.exe is not found in expected IGSS installation directories (IGSS may not be installed)
-
Check the installed version of Def.exeRight-click on Def.exe, select Properties, go to the Details tab and check the Product Version or File Version field. Alternatively, run: powershell (Get-Item 'C:\Program Files\Schneider Electric\IGSS\Def.exe').VersionInfoAffected if The reported version is 15.0.0.21140 or lower (versions prior to V15.0.0.21140 are vulnerable)
-
Confirm the vulnerable component is IGSS Definition moduleIn the Details tab of Def.exe, verify the Product Name contains 'IGSS Definition' or 'Interactive Graphical Scada System'. The vulnerability specifically affects the Definition module, not other IGSS componentsAffected if The installed component is IGSS Definition with a vulnerable version number
-
Assess CGF file import exposureCheck if users have the ability to import CGF files into IGSS Definition. This is typically done through the Definition interface via File > Import or similar menu options. Review if the IGSS Definition application is accessible to users who might import files from untrusted sourcesAffected if Users with access to IGSS Definition can import CGF files from external or untrusted sources
A user is affected if IGSS Definition (Def.exe) is installed with version 15.0.0.21140 or lower and users have the ability to import CGF files into the application.
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 dataUsers should avoid importing CGF files from untrusted sources until a vendor patch is applied. Organizations should update IGSS Definition to a patched version and implement file import validation controls at the network perimeter.
- Consultation4.0 h
- Implementation12.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22758 — 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-22758 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