Gs1900 10hp FirmwareOperating system · Zyxel

CVE-2015-5988

CRITICAL · 9.8 CVSS v3.0 Published 2015-12-31
Fix available
A fix is available. Upgrade to 2.50 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
The web management interface on Belkin F9K1102 2 devices with firmware 2.10.17 has a blank password, which allows remote attackers to obtain administrative privileges by leveraging a LAN session.

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 Belkin F9K1102 v2 router with firmware 2.10.17 ships with a blank administrator password on its web management interface, allowing any user with LAN network access to authenticate as admin without providing any credentials.

MitigationSet a strong administrative password immediately via the device's web interface; if the device is end-of-life and cannot receive firmware updates, replace it with a supported router.

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
Gs1900 10hp FirmwareOperating system
Affected:< 2.50\(aazi.0\)c0

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.0/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
    Access the device's web management interface or check the device label to confirm it is a Zyxel Gs1900 10hp switch
    Affected if The device is a Zyxel Gs1900 10hp
  2. Check the installed firmware version
    Log into the web management interface and navigate to the firmware or system information section, or use the command-line interface to display the firmware version
    Affected if The firmware version is earlier than 2.50(aazi.0)c0
  3. Verify web interface authentication behavior
    Attempt to access the web management interface using default or no credentials. Try accessing the admin login page and attempt authentication with a blank password
    Affected if Authentication succeeds with a blank or empty password
  4. Confirm administrator account configuration
    Log into the device and navigate to the administration or user management settings to examine whether the administrator password is set to blank or left empty
    Affected if The administrator password is blank or unset

A user is affected if the device is a Zyxel Gs1900 10hp running firmware prior to version 2.50(aazi.0)c0 with a blank administrator password on the web management interface.

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 2.50 or later
Fixed in 2.50
Interim mitigation

Set a strong administrative password immediately via the device's web interface; if the device is end-of-life and cannot receive firmware updates, replace it with a supported router.

Recommended fix Moderate confidence

Firmware version 2.50(aazi.0)c0 or later

  1. 1. Identify the exact model number and current firmware version of the affected device
  2. 2. Download the latest firmware version 2.50(aazi.0)c0 or later from the vendor's official support page
  3. 3. Access the device's web management interface
  4. 4. Navigate to the firmware upgrade or system settings section
  5. 5. Upload and apply the firmware update
  6. 6. After reboot, verify the new firmware version is installed
  7. 7. Change the default administrator password to a strong, unique password
  8. 8. Verify the new password is required for administrative access
Caveat Review vendor release notes for any configuration or feature changes before upgrading

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

Fix this in Gs1900 10hp Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-5988 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-5988 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