CVE-2018-17563
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/api-get_line_status on Grandstream GXP16xx VoIP 1.0.4.128 phones allows attackers to dump the device's configuration in cleartext.
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 confidenceThe Grandstream GXP16xx VoIP phone firmware 1.0.4.128 contains an information disclosure vulnerability in the /cgi-bin/api-get_line_status CGI endpoint. When a malformed input string is sent to this endpoint, the device responds by returning the device's full configuration data in cleartext, exposing potentially sensitive settings.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device model and firmware versionAccess the phone's web administration interface and navigate to the status or system information page to view the firmware version. Alternatively, check the device's display menu for firmware information.Affected if The device is a Grandstream GXP1610, GXP1615, GXP1620, GXP1625, GXP1628, or GXP1630 running firmware version 1.0.4.128
-
Verify network accessibility of the CGI endpointEnsure the device's web interface is reachable on the network by attempting to access http://<device_ip>/cgi-bin/api-get_line_status from a permitted network location.Affected if The /cgi-bin/api-get_line_status endpoint is accessible from the network without authentication
-
Test for information disclosure responseSend a malformed or unexpected input string (such as an empty request, special characters, or non-numeric input) to the endpoint using a tool like curl: curl -X POST http://<device_ip>/cgi-bin/api-get_line_status -d "malformed_input"Affected if The endpoint responds with cleartext configuration data including potentially sensitive settings such as SIP credentials, usernames, or other device parameters
You are affected if you have a Grandstream GXP16xx phone (models 1610/1615/1620/1625/1628/1630) running firmware exactly version 1.0.4.128 and the web interface is network-accessible, since sending malformed input to the api-get_line_status endpoint will expose full device configuration in cleartext.
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.
From vendor dataApply vendor firmware updates if available; otherwise, restrict network access to the device management interface via firewall rules or place devices in isolated network segments to limit exposure to unauthenticated attackers.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17563 — 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-17563 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