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

> Remote attackers can retrieve the administrator password without authentication by accessing a specific URL on the ASUS RT-N10E router.

- **Severity:** Medium 6.1 (`AV:A/AC:L/Au:N/C:C/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:** 5 Oct 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-64cv-c6cm-6vwf

## What is CVE-2013-3610?

CVE-2013-3610 is a medium-severity authentication bypass vulnerability in n/a, published on 5 Oct 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

qis/QIS_finish.htm on the ASUS RT-N10E router with firmware before 2.0.0.25 does not require authentication, which allows remote attackers to discover the administrator password via a direct request.

Weakness: CWE-287 (Improper Authentication)

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

It affects 2 products.


Products: Asus Rt-N10e, Asus Rt-N10e Firmware.

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

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

## Is CVE-2013-3610 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-3610 is a medium-severity authentication bypass vulnerability in n/a, published on 5 Oct 2013. 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-3610 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-3610/ (Markdown: https://insights.sbomify.com/CVE-2013-3610/index.md)
```

## Sources

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

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