# CVE-2012-6614: Privilege escalation in n/a

> Authenticated users can gain persistent root access on D-Link DSR-250N routers by exploiting the BusyBox CLI to overwrite the super user password.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4x5r-v8g2-7qhv

## What is CVE-2012-6614?

CVE-2012-6614 is a high-severity vulnerability in n/a, published on 19 Feb 2020. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

D-Link DSR-250N devices before 1.08B31 allow remote authenticated users to obtain "persistent root access" via the BusyBox CLI, as demonstrated by overwriting the super user password.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Dlink Dsr-250n Firmware.

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

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

## Is CVE-2012-6614 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-6613](https://insights.sbomify.com/CVE-2012-6613/): Hardcoded credentials in n/a (high 7.2)
- [CVE-2020-26567](https://insights.sbomify.com/CVE-2020-26567/): Missing authorization in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-6614 is a high-severity vulnerability in n/a, published on 19 Feb 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-6614 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-6614/ (Markdown: https://insights.sbomify.com/CVE-2012-6614/index.md)
```

## Sources

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

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