dbcve.org
Igss DashboardApplication · Schneider Electric

CVE-2023-3001

HIGH · 7.8 CVSS v3.1 Published 2023-06-14
Fix available
A fix is available. Upgrade to 16.0.0.23131 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
A CWE-502: Deserialization of Untrusted Data vulnerability exists in the Dashboard module that could cause an interpretation of malicious payload data, potentially leading to remote code execution when an attacker gets the user to open a malicious file.

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 confidence

A CWE-502 deserialization vulnerability exists in the Dashboard module where malicious payload data is deserialized without proper validation. An attacker can craft a malicious file that, when opened by a user, triggers unsafe deserialization leading to remote code execution.

MitigationImplement safe deserialization by using allowlist validation for deserialized classes, digital signatures for serialized data integrity, or migrate to safer data formats like JSON. Additionally, educate users about not opening untrusted files.

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
Igss DashboardApplication
Affected:< 16.0.0.23131

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Igss Dashboard installation location
    Locate the Schneider Electric Igss installation directory, typically found in Program Files or Program Files (x86). Look for files named 'igss.exe', 'Dashboard.exe', or similar Igss-related executables.
    Affected if The Dashboard executable exists in the Igss installation folder and the installed version is below 16.0.0.23131
  2. Determine installed version of Igss Dashboard
    Right-click the Dashboard executable (or igss.exe) and select Properties, then view the Details tab for version information. Alternatively, right-click the executable in Windows Explorer and choose Properties > Details.
    Affected if The version shown is less than 16.0.0.23131 (e.g., 16.0.0.x where x is less than 23131, or any earlier major version)
  3. Verify Dashboard module presence
    Open the Igss application and navigate to the Dashboard module or check the available modules in the Igss program menu. The vulnerability exists specifically in the Dashboard module.
    Affected if The Dashboard module is present and accessible in the Igss application
  4. Inspect file associations for Igss file types
    Check Windows file associations for .igss, .dat, or other proprietary Igss file extensions via Control Panel > Default Programs > Associate a file type or extension. These may be used with the deserialization feature.
    Affected if Igss file types are associated with the Dashboard or Igss application, indicating the deserialization pathway could be triggered by opening malicious files

You are affected if Schneider Electric Igss Dashboard is installed with a version lower than 16.0.0.23131 and the Dashboard module is present and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 16.0.0.23131 or later
Fixed in 16.0.0.23131
Interim mitigation

Implement safe deserialization by using allowlist validation for deserialized classes, digital signatures for serialized data integrity, or migrate to safer data formats like JSON. Additionally, educate users about not opening untrusted files.

Recommended fix High confidence

16.0.0.23131

  1. Obtain the fixed version (16.0.0.23131 or later) from the official Schneider Electric download portal at download.schneider-electric.com
  2. Back up all Igss Dashboard configuration files and any relevant data before proceeding with the upgrade
  3. Stop the Igss Dashboard service prior to installation
  4. Install version 16.0.0.23131 or later of Igss Dashboard
  5. Restart the Igss Dashboard service after installation completes
  6. Verify the Dashboard module loads correctly and the service is running without errors

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Igss Dashboard Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-3001 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-3001 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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