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

> Remote attackers can bypass authentication and gain administrator access on D-Link DSL-2740B Gateways if an admin session is active.

- **Severity:** High 7.6 (`AV:N/AC:H/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Nov 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-hvv6-ggwg-3qq9

## What is CVE-2013-2271?

CVE-2013-2271 is a high-severity authentication bypass vulnerability in n/a, published on 15 Nov 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The D-Link DSL-2740B Gateway with firmware EU_1.0, when an active administrator session exists, allows remote attackers to bypass authentication and gain administrator access via a request to login.cgi.

Weakness: CWE-264

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

It affects 2 products.


Products: Dlink Dsl-2740b, Dlink Dsl-2740b Firmware.

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

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

## Is CVE-2013-2271 being exploited?

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

Public exploit code:

- D-Link DSL-2740B ADSL Router - Authentication Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-5730](https://insights.sbomify.com/CVE-2013-5730/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-2271 is a high-severity authentication bypass vulnerability in n/a, published on 15 Nov 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-2271 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-2271/ (Markdown: https://insights.sbomify.com/CVE-2013-2271/index.md)
```

## Sources

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

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