# CVE-2013-3070: Information disclosure in n/a

> An attacker can access the wireless PSK via the management interface, exposing network credentials on Netgear WNDR4700 routers.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 14 Nov 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2c5f-68qc-5vrp

## What is CVE-2013-3070?

CVE-2013-3070 is a high-severity vulnerability in n/a, published on 14 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Information Disclosure vulnerability exists in Netgear WNDR4700 running firmware 1.0.0.34 in the management web interface, which discloses the PSK of the wireless LAN.

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

## Which versions are affected by CVE-2013-3070?

It affects 1 product.


Products: Netgear Wndr4700 Firmware.

## How do I fix CVE-2013-3070?

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

## Is CVE-2013-3070 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-3071](https://insights.sbomify.com/CVE-2013-3071/): Auth bypass in n/a (critical 9.8)
- [CVE-2013-3072](https://insights.sbomify.com/CVE-2013-3072/): Auth bypass in n/a (critical 9.8)
- [CVE-2013-3073](https://insights.sbomify.com/CVE-2013-3073/): Path traversal in n/a (critical 9.8)
- [CVE-2013-3074](https://insights.sbomify.com/CVE-2013-3074/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-3070 and fix it if it is affected.

What it is: CVE-2013-3070 is a high-severity vulnerability in n/a, published on 14 Nov 2019. 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-2013-3070 in the wild and no public exploit code.

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-2013-3070/ (Markdown: https://insights.sbomify.com/CVE-2013-3070/index.md)
```

## Sources

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

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