CVE-2018-17564
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 · uneditedA Malformed Input String to /cgi-bin/delete_CA on Grandstream GXP16xx VoIP 1.0.4.128 phones allows attackers to delete configuration parameters and gain admin access to the device.
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 · moderate confidenceThis is an injection vulnerability in the /cgi-bin/delete_CA endpoint on Grandstream GXP16xx VoIP phones running firmware 1.0.4.128. The malformed input string allows attackers to delete configuration parameters, which can lead to unauthorized admin access to the device.
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= 1.0.4.128= 1.0.4.128= 1.0.4.128= 1.0.4.128= 1.0.4.128= 1.0.4.128CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device web interface or send a SIP OPTIONS request to the device and look for the 'Server' or 'Model' header in the responseAffected if The device is NOT one of: GXP1610, GXP1615, GXP1620, GXP1625, GXP1628, or GXP1630
-
Verify the firmware versionLog into the device web interface and navigate to the Status or Maintenance page to view the firmware version, or query the device via SIP for version informationAffected if The firmware version is NOT exactly 1.0.4.128
-
Confirm the CGI endpoint existsSend an HTTP GET or POST request to http://<device_ip>/cgi-bin/delete_CA and observe the responseAffected if The endpoint returns a 404 or is not reachable at all (the device is not affected if the endpoint does not exist)
Your device is affected if it is a Grandstream GXP16xx model (1610/1615/1620/1625/1628/1630) running firmware version 1.0.4.128 and the /cgi-bin/delete_CA endpoint is present and accessible on the device.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply vendor firmware patch if available; otherwise isolate the affected VoIP devices on a restricted network segment and disable unauthenticated access to CGI endpoints.
Latest firmware version available from Grandstream for GXP16xx series (newer than 1.0.4.128)
- 1. Identify the exact model number of the Grandstream GXP device from the affected list (GXP1610, GXP1615, GXP1620, GXP1625, GXP1628, or GXP1630)
- 2. Navigate to the official Grandstream support website at grandstream.com
- 3. Locate the firmware download section for your specific GXP16xx model
- 4. Check for firmware versions newer than 1.0.4.128 that include security fixes
- 5. Download the latest stable firmware release from Grandstream's official source
- 6. Access the device web interface using admin credentials
- 7. Navigate to the firmware upgrade or maintenance section
- 8. Upload and apply the new firmware, ensuring stable power during the process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17564 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-17564 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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