dbcve.org
IfixApplication · Ge

CVE-2023-0598

CRITICAL · 9.8 CVSS v3.1 Published 2023-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
GE Digital Proficy iFIX 2022, GE Digital Proficy iFIX v6.1, and GE Digital Proficy iFIX v6.5 are vulnerable to code injection, which may allow an attacker to insert malicious configuration files in the expected web server execution path and gain full control of the HMI software.

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 · moderate confidence

GE Digital Proficy iFIX contains a code injection vulnerability in its web server component. Attackers can insert malicious configuration files into the expected web server execution path, enabling arbitrary code execution and full HMI software control. The vulnerability affects the 2022 release and v6.1/v6.5 of the industrial HMI platform.

MitigationImplement strict input validation on file paths and file names for configuration files, restrict web server write permissions to trusted directories only, and deploy file integrity monitoring on the web server execution path. Consider network segmentation to limit exposure.

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
IfixApplication
Affected:= 6.1= 6.5= 2022

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Identify installed iFIX version
    Open Windows Control Panel, navigate to Programs and Features, locate GE Digital Proficy iFIX and note the version column; alternatively, run 'reg query HKLM\SOFTWARE\GE Digital\iFIX\Setup' in Command Prompt to query the installed version from the registry
    Affected if The installed version is exactly 6.1, 6.5, or 2022
  2. Confirm web server component presence
    Check for the presence of the iFIX Web Server service or web server executable files in the iFIX installation directory (typically C:\Program Files\GE Digital\iFIX or C:\Program Files (x86)\GE Digital\iFIX); look for folders named 'WebServer', 'www', or similar web serving components
    Affected if The web server component is installed and the iFIX version is 6.1, 6.5, or 2022
  3. Inspect web server execution path for unauthorized config files
    Navigate to the web server root directory (commonly found under the iFIX installation under folders like WebServer\Config, www\config, or similar); list all configuration files (.xml, .json, .ini, .conf) and examine them for suspicious content or unexpected modifications
    Affected if Unexpected or newly created configuration files are present in the web server execution path
  4. Review web server directory file permissions
    Right-click the web server root folder, select Properties, then Security tab; verify which accounts have Write or Modify permissions; check Event Viewer for any unauthorized file creation events in web server directories
    Affected if Write permissions are granted to untrusted accounts or there are indicators of unauthorized file placement

If iFIX version 6.1, 6.5, or 2022 is installed with the web server component enabled, and unexpected configuration files exist in the web server execution path, the environment is affected by CVE-2023-0598.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation on file paths and file names for configuration files, restrict web server write permissions to trusted directories only, and deploy file integrity monitoring on the web server execution path. Consider network segmentation to limit exposure.

Fix this in Ifix Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-0598 — 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-0598 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