Gwn7610 FirmwareOperating system · Grandstream

CVE-2019-10658

HIGH · 8.8 CVSS v3.1 Published 2019-03-30
Fix available
A fix is available. Upgrade to 1.0.8.18 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Grandstream GWN7610 before 1.0.8.18 devices allow remote authenticated users to execute arbitrary code via shell metacharacters in the filename in a /ubus/controller.icc.update_nds_webroot_from_tmp update_nds_webroot_from_tmp API call.

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

Authenticated command injection vulnerability in Grandstream GWN7610 WiFi access points. The update_nds_webroot_from_tmp API endpoint does not sanitize shell metacharacters in the filename parameter, allowing authenticated remote attackers to execute arbitrary code on the affected device.

MitigationUpgrade firmware to version 1.0.8.18 or later. If immediate upgrade is not feasible, restrict administrative access to the device's web interface to trusted networks or IP addresses.

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
Gwn7610 FirmwareOperating system
Affected:< 1.0.8.18

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 web management interface and locate the device information page, or use SNMP/network discovery to identify the device model. Confirm it is a Grandstream GWN7610 WiFi access point.
    Affected if The device model is Grandstream GWN7610
  2. Check the firmware version
    In the web interface, navigate to the Status or System Info page to view the current firmware version. Alternatively, check via SNMP or the device's command-line interface if accessible.
    Affected if The installed firmware version is lower than 1.0.8.18
  3. Verify web interface accessibility
    Confirm the device's web management interface is reachable on the network. Since CVE-2019-10658 requires authentication, determine if the administrative interface is exposed to untrusted networks.
    Affected if The web interface is accessible from networks outside the trusted administrative zone
  4. Confirm authentication to the web interface
    Verify if default or known credentials are in use, or check whether user authentication is required to access the device's management functions.
    Affected if An attacker can obtain valid administrative credentials to access the update_nds_webroot_from_tmp API endpoint

The environment is affected if the device is a Grandstream GWN7610 running firmware version lower than 1.0.8.18 with its web interface accessible to untrusted users who can obtain administrative authentication.

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.

From vendor data
Upgrade available Upgrade to 1.0.8.18 or later
Fixed in 1.0.8.18
Interim mitigation

Upgrade firmware to version 1.0.8.18 or later. If immediate upgrade is not feasible, restrict administrative access to the device's web interface to trusted networks or IP addresses.

Fix this in Gwn7610 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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