# CVE-2012-2440: Misconfiguration in n/a

> Default router configuration exposes web administration on the WAN interface, allowing remote attackers to access the management interface without authentication.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Apr 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f6pm-r74q-rw7g

## What is CVE-2012-2440?

CVE-2012-2440 is a high-severity vulnerability in n/a, published on 28 Apr 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The default configuration of the TP-Link 8840T router enables web-based administration on the WAN interface, which allows remote attackers to establish an HTTP connection and possibly have unspecified other impact via unknown vectors.

Weakness: CWE-264

## Which versions are affected by CVE-2012-2440?

It affects 1 product.


Products: Tp-Link 8840t.

## How do I fix CVE-2012-2440?

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

## Is CVE-2012-2440 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2440 and fix it if it is affected.

What it is: CVE-2012-2440 is a high-severity vulnerability in n/a, published on 28 Apr 2012. 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-2012-2440 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-2012-2440/ (Markdown: https://insights.sbomify.com/CVE-2012-2440/index.md)
```

## Sources

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

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