CVE-2022-2952
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 · uneditedGE CIMPICITY versions 2022 and prior is vulnerable when data from a faulting address controls code flow starting at gmmiObj!CGmmiOptionContainer, 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 confidenceGE CIMPICITY versions 2022 and prior contains a vulnerability in the gmmiObj component (specifically at CGmmiOptionContainer) where data from a faulting address controls code flow, potentially allowing an attacker to execute arbitrary code. This appears to be a memory corruption vulnerability where attacker-controlled data influences execution pathways.
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<= 2022CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify GE Cimplicity installationSearch for Cimplicity installation directories (typically in Program Files or Program Files (x86)) and locate the main executable (Cimplicity.exe) or check Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\GE\Cimplicity for installation informationAffected if GE Cimplicity is installed and version is 2022 or prior (any version number <= 2022)
-
Determine installed Cimplicity versionRight-click the Cimplicity.exe executable, select Properties, and check the File Version field, or use the version information from the Windows Registry key identified in step 1Affected if The reported version number is 2022 or lower (for example, 2021, 2020, v10, etc.)
-
Verify presence of vulnerable gmmiObj componentSearch for the file gmmiObj.dll or gmmiObj.exe in the Cimplicity installation directory, typically under the bin or runtime subfolderAffected if The gmmiObj component file exists in the installation directory
-
Confirm CGmmiOptionContainer module is presentInspect the gmmiObj component file using a tool like dumpbin or a dependency walker to verify the presence of the CGmmiOptionContainer class/symbolAffected if The CGmmiOptionContainer module or symbol is found within the gmmiObj component
-
Assess network exposure of Cimplicity servicesReview network configuration and listening ports on the affected system, checking firewall rules and service configurations that expose Cimplicity to network accessAffected if Cimplicity services are accessible from untrusted network segments or the internet
A system is affected if GE Cimplicity version 2022 or prior is installed with the gmmiObj component present and exposed to network attackers, as the memory corruption flaw in CGmmiOptionContainer can be triggered by attacker-controlled data.
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 dataApply vendor-supplied patches for GE CIMPICITY when available. In the interim, restrict network access to affected systems, minimize the attack surface by disabling unnecessary services, and monitor for indicators of compromise.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2952 — 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-2022-2952 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