# CVE-2017-10932: Deserialization in NR8000 Series

> Unauthenticated remote attackers can execute arbitrary code on ZTE microwave devices via crafted Java RMI requests exploiting unsafe deserialization.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-m3q7-cc99-gc97

## What is CVE-2017-10932?

CVE-2017-10932 is a critical unsafe deserialization vulnerability in ZTE NR8000 Series, published on 27 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2017-10932?

It affects 6 products.


Products: Zte Nr8000tr Firmware, Zte Nr8120 Firmware, Zte Nr8120a Firmware, Zte Nr8150 Firmware, Zte Nr8250 Firmware, Zte Nr8950 Firmware.

## How do I fix CVE-2017-10932?

No fix has been published for CVE-2017-10932 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-10932 being exploited?

There is no known exploitation of CVE-2017-10932 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-10932 and fix it if it is affected.

What it is: CVE-2017-10932 is a critical unsafe deserialization vulnerability in ZTE NR8000 Series, published on 27 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-10932 in the wild and no public exploit code.

Affected product: ZTE NR8000 Series. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-10932/ (Markdown: https://insights.sbomify.com/CVE-2017-10932/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-10932
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-10932
- OSV: https://osv.dev/vulnerability/CVE-2017-10932

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-10932/
Summaries are generated and may contain mistakes; the official description above is the record.