dbcve.org
Nr8120 FirmwareOperating system · Zte

CVE-2017-10932

CRITICAL · 9.8 CVSS v3.1 Published 2017-09-28
Fix available
A fix is available. Upgrade to 12.17.20 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 V12.17.20 of the ZTE Microwave NR8000 series products - NR8120, NR8120A, NR8120, NR8150, NR8250, NR8000 TR and NR8950 are the applications of C/S architecture using 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

Java deserialization vulnerability in ZTE Microwave NR8000 series (NR8120, NR8120A, NR8150, NR8250, NR8000 TR, NR8950) using Apache Commons Collections library in their Java RMI service. Unauthenticated remote attackers can send crafted RMI requests to achieve arbitrary code execution on the target host.

MitigationUpgrade to version V12.17.20 or later to patch the vulnerable Apache Commons Collections library in the Java RMI service.

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
Nr8120 FirmwareOperating system
Affected:< 12.17.20
Nr8120a FirmwareOperating system
Affected:< 12.17.20
Nr8150 FirmwareOperating system
Affected:< 12.17.20
Nr8250 FirmwareOperating system
Affected:< 12.17.20
Nr8000tr FirmwareOperating system
Affected:< 12.17.20
Nr8950 FirmwareOperating system
Affected:< 12.17.20

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.1/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. Identify device model
    Access the device web interface or CLI and retrieve the hardware model information. Look for NR8120, NR8120A, NR8150, NR8250, NR8000 TR, or NR8950 identifiers in the system information or device status page.
    Affected if The device model is one of the listed NR8000 series variants.
  2. Check firmware version
    Navigate to the device web interface (typically via HTTP/HTTPS) and locate the firmware version in the system status, about, or firmware information page. Alternatively, use the CLI command 'show version' or 'display version' to retrieve the installed firmware version.
    Affected if The firmware version is lower than 12.17.20 (e.g., 12.16.x, 12.15.x, etc.).
  3. Verify Java RMI service exposure
    From an external network position, attempt to determine if port 1099 (default RMI registry port) or other RMI ports are open and accessible on the device IP address using a port scanner such as 'nmap -p 1099 <device_ip>' or 'nc -zv <device_ip> 1099'. Check device documentation or firewall rules to see if RMI service is enabled in the configuration.
    Affected if The Java RMI service port (commonly 1099) is open and exposed on the network, and the firmware version is below 12.17.20.
  4. Confirm Apache Commons Collections presence
    If you have administrative access to the device filesystem (via FTP, SCP, or debug mode if available), search for JAR files containing 'commons-collections' in the application directories, typically found in /usr/local, /opt, or similar paths. Use 'find . -name "*commons-collections*.jar"' to locate the library.
    Affected if The commons-collections library JAR file exists on the device filesystem and the firmware version is below 12.17.20.

The device is affected if it is a ZTE NR8000 series model (NR8120, NR8120A, NR8150, NR8250, NR8000 TR, or NR8950) running firmware version lower than 12.17.20 with the Java RMI service exposed on the network.

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 12.17.20 or later
Fixed in 12.17.20
Interim mitigation

Upgrade to version V12.17.20 or later to patch the vulnerable Apache Commons Collections library in the Java RMI service.

Recommended fix High confidence

Firmware V12.17.20 or later for NR8120, NR8120A, NR8150, NR8250, NR8000 TR, and NR8950

  1. 1. Obtain the firmware version V12.17.20 or later from the official ZTE support portal (support.zte.com.cn)
  2. 2. Access the ZTE Microwave NR8000 series device management interface
  3. 3. Navigate to the firmware upgrade section in the device management console
  4. 4. Upload and apply the firmware version V12.17.20 or later
  5. 5. After the upgrade completes, verify the firmware version has been updated successfully
  6. 6. Restart the device if required to ensure the new firmware is fully operational
  7. 7. Verify the Apache Commons Collections library has been updated or replaced in the new firmware version

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

Fix this in Nr8120 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-10932 — 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-10932 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