CVE-2020-7479
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 in IGSS (Versions 14 and prior using the service: IGSSupdate), which could allow a local user to execute processes that otherwise require escalation privileges when sending local network commands to the IGSS Update Service.
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 the IGSS Update Service (IGSSupdate) allows local unprivileged users to execute processes requiring elevated privileges by sending local network commands to the service. This affects IGSS versions 14 and prior.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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.
-
Identify if IGSS is installedCheck the Windows installed programs list or look for IGSS installation directories (commonly in C:\Program Files\Schneider Electric\IGSS or similar).Affected if IGSS (Interactive Graphical Scada System) is present on the system
-
Determine the installed IGSS versionLocate the IGSS version information, typically found in the program's properties or in an About dialog within the IGSS application, or check the version of igss.exe in the installation directory.Affected if The installed version is 14.0.0.20008 or lower (versions 14.0 through 14.0.0.20008 are affected)
-
Verify the IGSSupdate service existsOpen Windows Services (services.msc) and look for a service named 'IGSSupdate' or 'IGSS Update Service', or check running processes for igssupdate.exe.Affected if The IGSSupdate service is installed and present on the system
-
Confirm the service is runningIn Windows Services, check if the IGSSupdate service status is 'Running', or query via command line: sc query IGSSupdateAffected if The IGSSupdate service is currently running
-
Assess network exposure of the serviceCheck if the service is bound to network interfaces (not localhost only) by reviewing service configuration or using netstat to see listening ports associated with IGSSupdate.Affected if The service is accessible over the network or via localhost on ports used by IGSSupdate
A system is affected if it has IGSS version 14.0.0.20008 or lower installed with the IGSSupdate service running and accessible.
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
Implement proper authentication for the IGSSupdate service, restrict network access to authorized administrators only, and apply vendor patches when available. Consider network segmentation to limit local service exposure.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7479 — 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-7479 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