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

> Remote attackers can bypass authentication on Nisuta routers by sending a specific HTTP header, gaining unauthorized access to the management interface.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-62p6-qrcw-mhm9

## What is CVE-2013-7282?

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

### Official description

The management web interface on the Nisuta NS-WIR150NE router with firmware 5.07.41 and Nisuta NS-WIR300N router with firmware 5.07.36_NIS01 allows remote attackers to bypass authentication via a "Cookie: :language=en" HTTP header.

Weakness: CWE-287 (Improper Authentication)

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

It affects 4 products.


Products: Nisuta Ns-Wir150ne, Nisuta Ns-Wir150ne Firmware, Nisuta Ns-Wir300n, Nisuta Ns-Wir300n Firmware.

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

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

## Is CVE-2013-7282 being exploited?

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

Public exploit code:

- Nisuta NS-WIR150NE / NS-WIR300N Wireless Routers - Remote Management Web Interface Authentication Bypass (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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