dbcve.org
Zxiptv Epg FirmwareOperating system · Zte

CVE-2017-10934

CRITICAL · 9.8 CVSS v3.0 Published 2018-07-25
Fix available
A fix is available. Upgrade to 5.09.02.02t4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
All versions prior to V5.09.02.02T4 of the ZTE ZXIPTV-EPG product use the Java RMI service in which the servers use the Apache Commons Collections (ACC) library that may result in Java deserialization vulnerabilities. An unauthenticated remote attacker can exploit the vulnerabilities by sending a crafted RMI request to execute arbitrary code on the target host.

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

The ZTE ZXIPTV-EPG product's Java RMI service uses the Apache Commons Collections library, which contains known Java deserialization flaws. An unauthenticated remote attacker can send crafted RMI requests to achieve arbitrary code execution on the target host due to insecure deserialization of untrusted data.

MitigationUpgrade ZTE ZXIPTV-EPG to version V5.09.02.02T4 or later to obtain the patched Apache Commons Collections library; if immediate patching is not feasible, isolate the RMI service behind a firewall or disable it if unnecessary.

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
Zxiptv Epg FirmwareOperating system
Affected:< 5.09.02.02t4

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm ZTE ZXIPTV-EPG is installed
    Identify the product through its web interface (typically on port 8080 or 80), service process, or by reviewing network services listening on the system
    Affected if The product is present and running on the target host
  2. Check firmware version
    Access the ZXIPTV-EPG admin interface and navigate to System Information or About section to view the firmware version, or check version files in the system if CLI access is available
    Affected if The installed firmware version is lower than 5.09.02.02t4 (for example, 5.09.02.00, 5.08.x, or earlier)
  3. Verify RMI service is exposed
    Scan for open ports associated with RMI (commonly port 1099 or custom RMI registry ports) on the host using nmap or netstat: nmap -p 1099,1090,9000-9100 <target>
    Affected if Port 1099 or other RMI registry ports are open and accessible from the network
  4. Confirm library is vulnerable
    If file system access is available, locate the Commons Collections library (typically commons-collections*.jar) within the application deployment directory and check its version; vulnerable versions include 3.1, 3.2.1, and earlier
    Affected if The Apache Commons Collections library version is 3.2.1 or earlier, or if the library file cannot be found and the firmware is below the patched version

A host is affected if it runs ZTE ZXIPTV-EPG with firmware version below 5.09.02.02t4 and has the RMI service exposed on the network, making it vulnerable to unauthenticated remote code execution through deserialization attacks.

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.

dbcve · scoped
Upgrade available Upgrade to 5.09.02.02t4 or later
Fixed in 5.09.02.02t4
Interim mitigation

Upgrade ZTE ZXIPTV-EPG to version V5.09.02.02T4 or later to obtain the patched Apache Commons Collections library; if immediate patching is not feasible, isolate the RMI service behind a firewall or disable it if unnecessary.

Recommended fix High confidence

V5.09.02.02T4

  1. Identify the current firmware version of the ZTE ZXIPTV-EPG device
  2. Obtain the V5.09.02.02T4 firmware update from official ZTE sources (support.zte.com.cn)
  3. Follow ZTE's standard firmware upgrade procedure for the ZXIPTV-EPG device
  4. Verify the upgrade was successful by confirming the firmware version is V5.09.02.02T4 or later
  5. After upgrade, verify the RMI service is no longer vulnerable by confirming the Apache Commons Collections library has been patched or removed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zxiptv Epg Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-10934 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2017-10934 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