CVE-2021-22760
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-763: Release of invalid pointer or reference 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 missing checks 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 confidenceCWE-763 vulnerability in IGSS Definition (Def.exe) allows a malicious CGF file to trigger release of an invalid pointer due to missing validation of user-supplied input during file import. This can lead to memory corruption enabling data loss 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 the IGSS installation directory, typically found in C:\Program Files\Schneider Electric\IGSS\ or C:\Program Files (x86)\Schneider Electric\IGSS\Affected if Def.exe is not present, the product is not installed and this CVE does not apply
-
Determine IGSS Definition versionRight-click Def.exe, select Properties, then view the Details tab to find the File Version. Alternatively, open IGSS Definition and check Help > About for the full version number including buildAffected if The installed version is 15.0.0.21140 or earlier (versions up to and including 15.0.0.21140 are affected)
-
Verify CGF file import capabilityLaunch IGSS Definition and attempt to access the file import function. Look for File > Open, File > Import, or similar options that handle .cgf filesAffected if CGF file import is available and the user can open or import CGF files, making the vulnerability reachable
-
Check for IGSS core DLLsVerify the presence of core IGSS DLLs in the installation directory, such as igss15.exe and supporting libraries, confirming a complete IGSS installationAffected if IGSS Definition is installed as part of a full IGSS SCADA installation, the vulnerability exists in the Definition module
You are affected if IGSS Definition (Def.exe) version 15.0.0.21140 or earlier is installed and CGF file import functionality is accessible in your 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 dataUpgrade IGSS Definition to a patched version. Until then, do not import CGF files from untrusted sources into IGSS Definition.
- Consultation4.0 h
- Implementation16.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22760 — 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-22760 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