CVE-2020-7478
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-22: Improper Limitation of a Pathname to a Restricted Directory exists in IGSS (Versions 14 and prior using the service: IGSSupdate), which could allow a remote unauthenticated attacker to read arbitrary files from the IGSS server PC on an unrestricted or shared network when the IGSS Update Service is enabled.
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 path traversal vulnerability (CWE-22) exists in the IGSSupdate service affecting IGSS versions 14 and prior. Remote unauthenticated attackers can read arbitrary files from the server by manipulating path references in HTTP requests to the IGSS Update Service, bypassing directory restrictions.
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>= 14.0, < 14.0.0.20009CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Verify IGSS installation existsCheck for IGSS installation directories, typically under C:\Program Files\Schneider Electric\IGSS or C:\IGSS, or look for IGSS-related services using 'sc query' or in Windows Services consoleAffected if IGSS software is installed on the system
-
Determine installed IGSS versionCheck the IGSS version by viewing file properties of the main executable (commonly igss.exe in the installation directory) or via Windows Programs and Features, then compare against the affected range: 14.0.0.0 to 14.0.0.20008Affected if Installed version falls within >= 14.0.0.0 and < 14.0.0.20009
-
Check if IGSS Update Service is enabledOpen Windows Services (services.msc) and look for 'IGSSupdate' or 'IGSS Update Service', or run 'sc query' to enumerate services. Also check if the service process (typically igssupdater.exe or similar) is runningAffected if The IGSS Update Service is installed and set to run (whether currently running or not)
-
Verify network exposure of the update serviceRun 'netstat -an | findstr' for common IGSS update service ports (typically ports 1234 or 8080 for update services) or review firewall rules for IGSS-related listening services. Check if the service is bound to 0.0.0.0 (all interfaces) vs localhost onlyAffected if The IGSS Update Service is listening on a network-accessible interface (0.0.0.0)
A system is affected if it has IGSS version 14.0.0.0 through 14.0.0.20008 installed WITH the IGSS Update Service enabled and network-accessible, as the path traversal is only exploitable through that specific service.
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 data14.0.0.20009
Apply vendor-supplied patches for IGSS or disable the IGSS Update Service if not required, as the vulnerability is only exploitable when this service is enabled.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7478 — 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-2020-7478 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