dbcve.org
Multilink FirmwareOperating system · Ge

CVE-2016-2310

CRITICAL · 9.8 CVSS v3.1 Published 2016-06-09
Fix available
A fix is available. Upgrade to after 5.5.0 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
General Electric (GE) Multilink ML800, ML1200, ML1600, and ML2400 switches with firmware before 5.5.0 and ML810, ML3000, and ML3100 switches with firmware before 5.5.0k have hardcoded credentials, which allows remote attackers to modify configuration settings via the web interface.

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

GE Multilink switches (ML800, ML1200, ML1600, ML2400, ML810, ML3000, ML3100) contain hardcoded credentials embedded in the firmware. Attackers can use these backdoor accounts to authenticate to the web management interface and modify device configuration settings remotely.

MitigationUpgrade firmware to version 5.5.0 (for ML800/ML1200/ML1600/ML2400) or 5.5.0k (for ML810/ML3000/ML3100). If immediate patching is not possible, restrict web interface access to trusted networks or disable remote web management.

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
Multilink FirmwareOperating system
Affected:<= 5.5.0<= 5.5.0k

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
    Log into the device CLI or check the web management interface to confirm the exact model number (ML800, ML1200, ML1600, ML2400, ML810, ML3000, or ML3100).
    Affected if The device is a GE Multilink switch in the listed model range.
  2. Check the installed firmware version
    Access the device CLI or web interface and look for the firmware version information, typically found in system status or device info sections.
    Affected if The firmware version is 5.5.0 or earlier for ML800/ML1200/ML1600/ML2400, or 5.5.0k or earlier for ML810/ML3000/ML3100.
  3. Verify if the web management interface is enabled
    Check the device configuration for web interface status, typically under management settings or HTTP/HTTPS service configuration.
    Affected if The web management interface is enabled and accessible.
  4. Review user accounts on the device
    Access the device user account configuration and list all configured accounts, looking for any unexpected or undocumented accounts beyond normal administrator accounts.
    Affected if Unexpected or undocumented accounts exist on the device.
  5. Inspect web interface access logs
    Review the web management interface logs or system logs for authentication events, particularly from unknown IP addresses or at unusual times.
    Affected if Successful logins occurred from unexpected accounts or IP addresses.

You are affected if you have a GE Multilink switch (ML800/ML1200/ML1600/ML2400/ML810/ML3000/ML3100) running firmware version 5.5.0 or earlier (or 5.5.0k or earlier) with the web management interface enabled and any backdoor accounts present or used.

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 5.5.0
Interim mitigation

Upgrade firmware to version 5.5.0 (for ML800/ML1200/ML1600/ML2400) or 5.5.0k (for ML810/ML3000/ML3100). If immediate patching is not possible, restrict web interface access to trusted networks or disable remote web management.

Recommended fix High confidence

Firmware 5.5.0 (for ML800/ML1200/ML1600/ML2400) or 5.5.0k (for ML810/ML3000/ML3100)

  1. 1. Identify the exact Multilink switch model (ML800, ML1200, ML1600, ML2400, ML810, ML3000, or ML3100)
  2. 2. Determine the current firmware version by accessing the web interface or using CLI
  3. 3. Download the appropriate firmware update from the GE/Industrial Networks support portal: for ML800/ML1200/ML1600/ML2400 download firmware 5.5.0 or later; for ML810/ML3000/ML3100 download firmware 5.5.0k or later
  4. 4. Review the firmware release notes for any prerequisites or special instructions
  5. 5. Backup the current switch configuration through the web interface or CLI
  6. 6. Schedule a maintenance window as firmware updates may cause brief network interruption
  7. 7. Upload the new firmware file through the web interface (System > Firmware Upgrade) or CLI
  8. 8. After upgrade completes, verify the new firmware version is installed
Caveat Firmware upgrades may temporarily interrupt network connectivity; review release notes for any configuration or feature changes

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

Fix this in Multilink Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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