# CVE-2013-3317: Auth bypass in n/a

> Attackers can bypass authentication on Netgear WNR1000v3 routers using the NtgrBak key, gaining unauthorized access to the device.

- **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:** 29 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jv9f-866g-rcwh

## What is CVE-2013-3317?

CVE-2013-3317 is a critical authentication bypass vulnerability in n/a, published on 29 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Netgear WNR1000v3 with firmware before 1.0.2.60 contains an Authentication Bypass via the NtgrBak key.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Netgear Wnr1000 Firmware.

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

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

## Is CVE-2013-3317 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-20488](https://insights.sbomify.com/CVE-2019-20488/): Command injection in n/a (critical 9.8)
- [CVE-2019-20489](https://insights.sbomify.com/CVE-2019-20489/): Auth bypass in n/a (critical 9.8)
- [CVE-2013-3316](https://insights.sbomify.com/CVE-2013-3316/): Auth bypass in n/a (critical 9.8)
- [CVE-2019-20487](https://insights.sbomify.com/CVE-2019-20487/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2019-20486](https://insights.sbomify.com/CVE-2019-20486/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-3317 is a critical authentication bypass vulnerability in n/a, published on 29 Jan 2020. 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-3317 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-3317/ (Markdown: https://insights.sbomify.com/CVE-2013-3317/index.md)
```

## Sources

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

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