CVE-2022-32528
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-306: Missing Authentication for Critical Function vulnerability exists that could cause access to manipulate and read specific files in the IGSS project report directory, potentially leading to a denial-of-service condition when an attacker sends specific messages. Affected Products: IGSS Data Server - IGSSdataServer.exe (Versions prior to V15.0.0.22170)
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 missing authentication vulnerability (CWE-306) in IGSS Data Server (IGSSdataServer.exe) allows unauthenticated attackers to manipulate and read specific files in the project report directory. By sending specific messages to the server, an attacker can trigger file operations without credentials, potentially causing denial-of-service through file manipulation.
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.22170CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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 Data Server processOpen Task Manager or use command 'tasklist | findstr IGSSdataServer' to find IGSSdataServer.exe running on the systemAffected if IGSSdataServer.exe is running and exposed to network
-
Check IGSS application versionLook in the IGSS installation directory (typically C:\Program Files\Schneider Electric\IGSS\) for version information in the application properties or check the file version of IGSSdataServer.exe by right-clicking the file and viewing Properties > DetailsAffected if Installed version is 15.0.0.22170 or lower
-
Verify network exposure of IGSS serviceCheck firewall rules and port listeners for IGSS data server ports (default ports may include TCP 12397, 12398, 12399) using 'netstat -an | findstr 1239' or review Windows Firewall inbound rulesAffected if IGSS Data Server ports are open to untrusted network addresses or the internet
-
Inspect project report directory accessibilityLocate the project report directory (typically in the IGSS project folder) and verify file permissions - check if the account running IGSSdataServer has read/write access to this directoryAffected if Project report directory exists and is accessible by the IGSS service account without authentication
If IGSSdataServer.exe is running with version 15.0.0.22170 or lower and is network-accessible, the system is vulnerable to unauthenticated file manipulation attacks.
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.
dbcve · scopedUpgrade IGSS Data Server to version V15.0.0.22170 or later to obtain the patched version with proper authentication controls. If immediate upgrade is not possible, network segmentation and firewall rules should restrict access to the IGSSdataServer service to trusted IP addresses only.
IGSS V15.0.0.22170 or later
- 1. Identify all IGSS (Interactive Graphical Scada System) installations in the environment.
- 2. Verify current version of IGSS Data Server (IGSSdataServer.exe) on each system.
- 3. If version is prior to V15.0.0.22170, download the updated IGSS V15.0.0.22170 or later from the official Schneider Electric download portal (download.schneider-electric.com).
- 4. Schedule maintenance window as IGSS may require restart during upgrade.
- 5. Back up existing IGSS project files and configuration before upgrade.
- 6. Apply the upgrade to IGSS Data Server on all affected systems.
- 7. Verify the upgrade was successful by checking the new version number.
- 8. Test IGSS functionality to ensure normal operations resumed.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32528 — 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-2022-32528 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