CVE-2017-10937
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 · uneditedSQL injection vulnerability in all versions prior to V2.01.05.09 of the ZTE ZXIPTV-UCM product allows remote attackers to execute arbitrary SQL commands via the opertype parameter, resulting in the disclosure of database information.
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 opertype parameter of ZTE ZXIPTV-UCM allows remote attackers to inject arbitrary SQL commands. This affects all versions prior to V2.01.05.09 and can lead to unauthorized database information disclosure.
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< 2.01.05.09CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 if the target system is ZTE ZXIPTV-UCMAccess the web interface or administrative panel of the system and look for product identification strings, or check the firmware file name and banner information during network enumerationAffected if The system is confirmed to be a ZTE ZXIPTV-UCM device
-
Determine the installed firmware versionLog into the administrative interface and navigate to the system information, status, or about page to locate the firmware version string, or extract the version from the firmware binary if accessibleAffected if The displayed version is lower than V2.01.05.09 or the version cannot be determined (treat as potentially affected)
-
Locate the opertype parameter endpointIdentify web endpoints that accept the opertype parameter, typically in forms or API calls related to user or operations management within the ZXIPTV-UCM web applicationAffected if The opertype parameter is found in any HTTP request handling user or operational functions
-
Check if the opertype parameter accepts SQL injection payloadsSend a test HTTP request with a benign SQL injection payload in the opertype parameter (e.g., opertype=1' OR '1'='1) and observe the application's response for SQL syntax errors or unexpected database-like behaviorAffected if The application returns database error messages, unusual data, or behaves differently compared to normal requests, indicating SQL injection is possible
A user is affected if the system is a ZTE ZXIPTV-UCM device running firmware version lower than V2.01.05.09 and the opertype parameter is accessible and vulnerable to SQL injection.
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 data2.01.05.09
Upgrade ZTE ZXIPTV-UCM to version V2.01.05.09 or later to patch the SQL injection vulnerability. If immediate patching is not possible, implement input validation and Web Application Firewall (WAF) controls on the opertype parameter as a compensating control.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10937 — 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-2017-10937 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