CVE-2021-22752
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 loss of data or remote code execution due to missing size checks, when a malicious WSP (Workspace) file is being parsed by 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 confidenceOut-of-bounds write vulnerability in Schneider Electric IGSS Definition (Def.exe) V15.0.0.21140 and prior caused by missing size checks during WSP (Workspace) file parsing. A specially crafted malicious WSP file can trigger a CWE-787 condition, potentially allowing an attacker to overwrite memory boundaries and achieve 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 installationSearch for Def.exe in typical installation directories such as C:\Program Files\Schneider Electric\IGSS\Definition\ or use file system search for Def.exeAffected if Def.exe is found on the system
-
Determine Def.exe versionRight-click Def.exe, select Properties, then view the Details tab for Product Version, or run: powershell (Get-Item 'C:\Program Files\Schneider Electric\IGSS\Definition\Def.exe').VersionInfo.ProductVersionAffected if Version is 15.0.0.21140 or lower (any version up to and including 21140)
-
Verify affected version rangeCompare installed version to 15.0.0.21140 using numeric comparison (e.g., 15.0.0.21140, 15.0.0.20000, 14.0.0.18000 would all be affected)Affected if Version number is less than or equal to 15.0.0.21140
-
Confirm WSP file handling is availableIGSS Definition processes WSP workspace files by default; verify the application can open .wsp files by checking file association or attempting to locate sample WSP files in the workspace directoryAffected if The application can load WSP files (this is the default functionality)
If IGSS Definition Def.exe version 15.0.0.21140 or lower is installed and can process WSP files, the environment is vulnerable to this out-of-bounds write flaw when opening a malicious WSP file.
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 dataAvoid opening untrusted WSP workspace files; obtain and apply vendor patch; implement file validation and sandboxing for IGSS Definition until patched version is available.
- Consultation2.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,400.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22752 — 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-22752 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