CVE-2019-10663
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 · uneditedGrandstream UCM6204 before 1.0.19.20 devices allow remote authenticated users to conduct SQL injection attacks via the sord parameter in a listCodeblueGroup API call to the /cgi? URI.
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 confidenceSQL injection vulnerability in the sord parameter of the listCodeblueGroup API endpoint (/cgi?) in Grandstream UCM6204 devices prior to version 1.0.19.20. Authenticated remote attackers can inject malicious SQL queries through this parameter.
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.19.20CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device admin interface or check the device label/marketing materials to confirm it is a Grandstream UCM6204 VoIP gateway. The model number is typically visible on the device itself or in the web interface header.Affected if The device is a Grandstream UCM6204 model
-
Check the installed firmware versionLog into the UCM6204 web administration interface and navigate to the System Status or About page to view the current firmware version. Alternatively, check via CLI if SSH/Telnet access is available.Affected if The firmware version is any version prior to 1.0.19.20 (e.g., 1.0.18.x, 1.0.17.x, etc.)
-
Verify the /cgi API endpoint is accessibleConfirm network accessibility to the device's web interface on port 8089 or 443, and check if the /cgi endpoint responds to requests. This can be done by attempting a curl or similar request to http://[device-ip]/cgi? or reviewing firewall/network access lists.Affected if The /cgi endpoint is reachable from a network where an authenticated attacker could send requests
-
Confirm authentication is enabled on the APIReview the UCM6204 user account settings and API access controls to determine if authentication is required for the /cgi endpoint, and verify whether default or weak credentials are in use.Affected if An attacker can obtain valid authentication credentials to access the listCodeblueGroup API endpoint
You are affected if you have a Grandstream UCM6204 device running firmware version lower than 1.0.19.20 and the /cgi API endpoint is accessible to an authenticated attacker.
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 data1.0.19.20
Upgrade UCM6204 firmware to version 1.0.19.20 or later. If immediate patching is not feasible, implement network segmentation and restrict access to the /cgi? API endpoint to trusted, authorized users only.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.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 $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10663 — 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-2019-10663 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