dbcve.org
Ms 3000 FirmwareOperating system · Ge

CVE-2022-43976

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 in FC46-WebBridge on GE Grid Solutions MS3000 devices before 3.7.6.25p0_3.2.2.17p0_4.7p0. Direct access to the API is possible on TCP port 8888 via programs located in the cgi-bin folder without any authentication.

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 FC46-WebBridge component on GE Grid Solutions MS3000 devices allows unauthenticated direct API access via TCP port 8888 through cgi-bin programs. This authentication bypass allows remote attackers to access sensitive grid management functions without credentials.

MitigationUpdate MS3000 firmware to version 3.7.6.25p0_3.2.2.17p0_4.7p0 or later. As an immediate compensating control, block unauthenticated access to TCP port 8888 via network segmentation or firewall rules.

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. Confirm target device is a GE MS3000
    Identify the device by checking system information, device labeling, or network inventory. The MS3000 is a GE Grid Solutions motor starter/controller used in industrial grid applications.
    Affected if The device is a GE Grid Solutions MS3000 motor controller
  2. Check firmware version
    Access the device admin interface or use vendor-specific commands to retrieve the installed firmware version. Compare the version number against the affected range: versions below 3.7.6.25p0_3.2.2.17p0_4.7p0 are vulnerable.
    Affected if Firmware version is below 3.7.6.25p0_3.2.2.17p0_4.7p0
  3. Verify TCP port 8888 is accessible
    Perform a port scan or connectivity test from an external host to TCP port 8888 on the device. Use tools such as netcat, nmap, or PowerShell Test-NetConnection.
    Affected if TCP port 8888 is open and accepting connections from untrusted networks
  4. Confirm WebBridge CGI-bin endpoint exposure
    Attempt to access the WebBridge cgi-bin API endpoint directly via port 8888 without providing credentials. For example: http://<device_ip>:8888/cgi-bin/
    Affected if The CGI-bin interface responds without requiring authentication

The device is affected if it is a GE MS3000 with firmware below version 3.7.6.25p0_3.2.2.17p0_4.7p0 AND TCP port 8888 is externally accessible, allowing unauthenticated access to the WebBridge CGI-bin API.

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 MS3000 firmware to version 3.7.6.25p0_3.2.2.17p0_4.7p0 or later. As an immediate compensating control, block unauthenticated access to TCP port 8888 via network segmentation or firewall rules.

Recommended fix High confidence

Upgrade to MS3000 Firmware version 3.7.6.25p0_3.2.2.17p0_4.7p0 or later

  1. 1. Identify the current firmware version of the GE Grid Solutions MS3000 device by accessing the device management interface or checking system information.
  2. 2. Compare the current version against the fixed release 3.7.6.25p0_3.2.2.17p0_4.7p0.
  3. 3. If the current firmware version is below 3.7.6.25p0_3.2.2.17p0_4.7p0, obtain the firmware update from GE Grid Solutions official support channels.
  4. 4. Follow GE's documented firmware upgrade procedure for MS3000 devices, ensuring stable power during the update process.
  5. 5. After upgrading, verify the new firmware version is 3.7.6.25p0_3.2.2.17p0_4.7p0 or later.
  6. 6. Confirm that API access on TCP port 8888 now requires authentication and direct cgi-bin access without credentials is no longer possible.
Caveat Review GE Grid Solutions release notes for any compatibility considerations or operational changes introduced in the new firmware version before deploying in production environments

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
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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