dbcve.org
CimplicityApplication · Ge

CVE-2022-3084

HIGH · 7.8 CVSS v3.1 Published 2022-12-08
Fix available
A fix is available. Upgrade to after 2022 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
GE CIMPICITY versions 2022 and prior is vulnerable when data from a faulting address controls code flow starting at gmmiObj!CGmmiRootOptionTable, which could allow an attacker to execute arbitrary code.

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 CIMPICITY versions 2022 and prior contains a memory corruption vulnerability in the gmmiObj!CGmmiRootOptionTable component where data from a faulting address controls code flow, potentially allowing arbitrary code execution. This appears to be a memory safety issue (likely a write-what-where or similar control-flow hijack) in the CGmmiRootOptionTable handling code.

MitigationUpgrade to a patched version of GE CIMPICITY that addresses this memory corruption vulnerability in the CGmmiRootOptionTable component. If patching is not immediately possible, restrict network access to affected systems and monitor for exploitation attempts.

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
CimplicityApplication
Affected:<= 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
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. Confirm GE Cimplicity is installed
    Check for the presence of the GE Cimplicity installation directory, typically found at C:\Program Files\GE Digital\Cimplicity or C:\Program Files (x86)\GE Digital\Cimplicity. Verify the Cimplicity software is installed on the system.
    Affected if GE Cimplicity software is present on the system
  2. Identify installed Cimplicity version
    Locate the version information in the installation directory, typically in a version.txt, about dialog, or check the executable version properties of the main Cimplicity executable (often named Cimplicity.exe or similar in the bin folder). Compare the version number to the affected range: versions 2022 and prior.
    Affected if The installed version is 2022 or any prior version (e.g., 2021, 2020, v10, etc.)
  3. Verify vulnerable gmmiObj component exists
    Check for the presence of the gmmiObj module (typically gmmiObj.dll) in the Cimplicity installation directory, particularly in the bin or system folders. This module contains the CGmmiRootOptionTable component.
    Affected if The gmmiObj.dll file exists in the Cimplicity installation folder
  4. Check if CGmmiRootOptionTable feature is in use
    Review Cimplicity project configurations or look for references to CGmmiRootOptionTable in project files, logs, or configuration settings. This component is part of the Cimplicity HMI/SCADA functionality.
    Affected if The system uses Cimplicity projects or configurations that load the gmmiObj module containing CGmmiRootOptionTable

A system is affected if GE Cimplicity version 2022 or prior is installed and the gmmiObj module containing CGmmiRootOptionTable is present and loaded.

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 a release after 2022
Interim mitigation

Upgrade to a patched version of GE CIMPICITY that addresses this memory corruption vulnerability in the CGmmiRootOptionTable component. If patching is not immediately possible, restrict network access to affected systems and monitor for exploitation attempts.

Recommended fix Moderate confidence

GE Cimplicity 2023 or later release

  1. 1. Check the current installed GE Cimplicity version by accessing the Cimplicity Project Editor or viewing the installation details.
  2. 2. Identify all Cimplicity installations in the environment that may be affected, including any distributed configurations.
  3. 3. Obtain the latest GE Cimplicity release from the official GE Digital support portal or contact GE Digital directly for the patched version.
  4. 4. Before upgrading, back up all Cimplicity project files, configurations, and databases.
  5. 5. Schedule a maintenance window as the upgrade may require stopping Cimplicity services.
  6. 6. Install the updated Cimplicity version (2023 or later) following the GE installation documentation.
  7. 7. Verify that the CGmmiRootOptionTable component is properly loaded and the vulnerability is addressed.
  8. 8. Test critical HMI operations and control workflows to ensure functionality is maintained after the upgrade.
Caveat Newer versions may introduce interface changes; thoroughly review release notes and test configurations before deploying to production

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

Fix this in Cimplicity Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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