# CVE-2016-10175: Information disclosure in n/a

> An attacker can retrieve the router's serial number via a specific URI, which facilitates obtaining administrator credentials when combined with another vulnerability.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 30 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-ghhf-xp94-4ggw

## What is CVE-2016-10175?

CVE-2016-10175 is a critical vulnerability in n/a, published on 30 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The NETGEAR WNR2000v5 router leaks its serial number when performing a request to the /BRS_netgear_success.html URI. This serial number allows a user to obtain the administrator username and password, when used in combination with the CVE-2016-10176 vulnerability that allows resetting the answers to the password-recovery questions.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2016-10175?

It affects 1 product.


Products: Netgear Wnr2000v5 Firmware.

## How do I fix CVE-2016-10175?

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

## Is CVE-2016-10175 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-10175 exists.

Public exploit code:

- NETGEAR WNR2000v5 Administrator Password Recovery (metasploit)
- Netgear WNR2000v5 - Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2016-10176](https://insights.sbomify.com/CVE-2016-10176/): Missing authorization in n/a (critical 9.8)
- [CVE-2021-29069](https://insights.sbomify.com/CVE-2021-29069/): Command injection in n/a (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10175 and fix it if it is affected.

What it is: CVE-2016-10175 is a critical vulnerability in n/a, published on 30 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-10175 exists.

Affected product: n/a. 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-2016-10175/ (Markdown: https://insights.sbomify.com/CVE-2016-10175/index.md)
```

## Sources

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

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