# CVE-2017-10874: Other in PWR-Q200

> Remote attackers can poison DNS caches on PWR-Q200 routers due to predictable source ports, potentially redirecting user traffic.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8hqr-v5jq-x64w

## What is CVE-2017-10874?

CVE-2017-10874 is a high-severity vulnerability in NIPPON TELEGRAPH AND TELEPHONE EAST CORPORATION PWR-Q200, published on 1 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PWR-Q200 does not use random values for source ports of DNS query packets, which allows remote attackers to conduct DNS cache poisoning attacks.

Weakness: CWE-330 (Use of Insufficiently Random Values)

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

It affects 1 product.


Products: Ntt-East Pwr-Q200 Firmware.

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

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

## Is CVE-2017-10874 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-10874 is a high-severity vulnerability in NIPPON TELEGRAPH AND TELEPHONE EAST CORPORATION PWR-Q200, published on 1 Dec 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-10874 in the wild and no public exploit code.

Affected product: NIPPON TELEGRAPH AND TELEPHONE EAST CORPORATION PWR-Q200. 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-10874/ (Markdown: https://insights.sbomify.com/CVE-2017-10874/index.md)
```

## Sources

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

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