dbcve.org
Ms 3000 FirmwareOperating system · Ge

CVE-2022-43975

HIGH · 7.5 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 →
84/100
Remediation priority · High
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. A vulnerability in the web server allows arbitrary files and configurations to be read via directory traversal over TCP port 8888.

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

A directory traversal vulnerability in the FC46-WebBridge component of GE Grid Solutions MS3000 devices allows unauthenticated attackers to read arbitrary files and configurations by manipulating path traversal sequences in HTTP requests to TCP port 8888. This affects versions prior to 3.7.6.25p0_3.2.2.17p0_4.7p0.

MitigationUpdate FC46-WebBridge to version 3.7.6.25p0_3.2.2.17p0_4.7p0 or later. Additionally, restrict network access to TCP port 8888 via firewall rules or network segmentation to minimize 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
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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 MS3000 device presence
    Identify if the target system is a GE Grid Solutions MS3000 device by checking the device model, hostname, or system information documentation. This CVE specifically affects MS3000 firmware.
    Affected if The system is a GE Grid Solutions MS3000 device.
  2. Check MS3000 firmware version
    Access the device management interface or use SNMP/CLI commands to retrieve the current firmware version. Compare the installed version string to the affected range: versions prior to 3.7.6.25p0_3.2.2.17p0_4.7p0 are vulnerable.
    Affected if The installed firmware version is older than 3.7.6.25p0_3.2.2.17p0_4.7p0.
  3. Verify TCP port 8888 accessibility
    Scan the device or network to determine if TCP port 8888 (the FC46-WebBridge service port) is exposed and reachable from untrusted networks. Use a port scanner such as nmap: nmap -p 8888 <target>
    Affected if TCP port 8888 is accessible from network segments that are not trusted or are external.
  4. Inspect network access controls
    Review firewall rules, access control lists, or network segmentation configurations that govern access to port 8888 on the MS3000 device. Check if the port is exposed to untrusted networks or the internet.
    Affected if No firewall or network segmentation restricts access to port 8888, or the port is reachable from untrusted/external networks.

A user is affected if they have a GE MS3000 device with firmware older than 3.7.6.25p0_3.2.2.17p0_4.7p0 AND TCP port 8888 is accessible from any network segment that is not fully trusted.

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 FC46-WebBridge to version 3.7.6.25p0_3.2.2.17p0_4.7p0 or later. Additionally, restrict network access to TCP port 8888 via firewall rules or network segmentation to minimize exposure.

Recommended fix High confidence

MS3000 Firmware version 3.7.6.25p0_3.2.2.17p0_4.7p0

  1. Obtain the fixed firmware version 3.7.6.25p0_3.2.2.17p0_4.7p0 from GE Grid Solutions through official support channels
  2. Review GE Grid Solutions MS3000 firmware upgrade documentation for physical device access requirements
  3. Ensure the device is backed up and in a stable state before initiating the upgrade
  4. Upload and apply the firmware update via the device management interface or console
  5. Verify the firmware version has been successfully updated to 3.7.6.25p0_3.2.2.17p0_4.7p0
  6. Confirm the FC46-WebBridge service on TCP port 8888 is operational and the path traversal vulnerability is resolved
Caveat Industrial device firmware upgrades may require physical access and could affect running operations; ensure proper change management and have a rollback plan

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

Fix this in Ms 3000 Firmware 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-43975 — 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-43975 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