dbcve.org
Ms 3000 FirmwareOperating system · Ge

CVE-2022-43977

CRITICAL · 9.8 CVSS v3.1 Published 2023-01-17
Fix available
A fix is available. Upgrade to 3.7.6.25p0_3.2.2.17p0_4.7p0 or later.
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
An issue was discovered on GE Grid Solutions MS3000 devices before 3.7.6.25p0_3.2.2.17p0_4.7p0. The debug port accessible via TCP (a qconn service) lacks access control.

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

The GE Grid Solutions MS3000 devices contain a qconn debug service listening on TCP that lacks any access control or authentication mechanisms. This allows unauthenticated remote attackers to potentially access the debug interface, which could enable arbitrary command execution or sensitive data access on these industrial control devices.

MitigationUpdate firmware to version 3.7.6.25p0_3.2.2.17p0_4.7p0 or later. Until patched, network-segment devices and block external access to the qconn TCP port.

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
Ms 3000 FirmwareOperating system
Affected:< 3.7.6.25p0_3.2.2.17p0_4.7p0

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 the device model
    Check the device label, web interface, or SNMP sysDescr for 'GE MS3000' or 'Grid Solutions MS3000' to confirm the device is a GE MS3000 industrial controller
    Affected if The device is not a GE MS3000, then this CVE does not apply
  2. Determine the installed firmware version
    Access the device web interface, check the system info page, or use the device's CLI command to retrieve the firmware version (typically found under 'System', 'About', or 'Version' menus)
    Affected if The firmware version is 3.7.6.25p0_3.2.2.17p0_4.7p0 or higher, then the device is not affected by this CVE. Versions below this threshold are vulnerable
  3. Check if qconn service is listening
    Perform a TCP port scan of the device or check open ports via the device's network diagnostics. Look for the qconn service typically on port 9090/tcp or commonly used debug ports
    Affected if The qconn TCP service is not exposed or not running, then exploitation is not possible regardless of version
  4. Verify network accessibility of qconn port
    From an unauthorized external host, attempt to TCP connect to the suspected qconn port on the device. Check firewall rules or access control lists that may restrict access to this service
    Affected if The qconn port is accessible from untrusted networks without authentication, the device is vulnerable to unauthenticated remote exploitation

The device is affected if it is a GE MS3000 with firmware version below 3.7.6.25p0_3.2.2.17p0_4.7p0 AND has the qconn TCP debug service exposed and accessible from the network.

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 3.7.6.25p0_3.2.2.17p0_4.7p0 or later
Fixed in 3.7.6.25p0_3.2.2.17p0_4.7p0
Interim mitigation

Update firmware to version 3.7.6.25p0_3.2.2.17p0_4.7p0 or later. Until patched, network-segment devices and block external access to the qconn TCP port.

Recommended fix Moderate confidence

3.7.6.25p0_3.2.2.17p0_4.7p0 or later

  1. Obtain the firmware version 3.7.6.25p0_3.2.2.17p0_4.7p0 or later from GE Grid Solutions official channels
  2. Review GE Grid Solutions MS3000 firmware upgrade documentation
  3. Ensure the upgrade process is conducted in a controlled environment
  4. Follow the vendor's standard firmware update procedure for the MS3000 device
  5. After upgrade, verify the qconn service is no longer exposed or is properly access-controlled
  6. Confirm the device is functioning normally post-upgrade

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

Fix this in Ms 3000 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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