# CVE-2012-6613: Hardcoded credentials in n/a

> Attackers can gain persistent root access to D-Link DSR-250N routers using the default admin password, compromising the device.

- **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:** 25 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xvh8-g3fx-684w

## What is CVE-2012-6613?

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

### Official description

D-Link DSR-250N devices with firmware 1.05B73_WW allow Persistent Root Access because of the admin password for the admin account.

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

It affects 1 product.


Products: Dlink Dsr-250n Firmware.

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

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

## Is CVE-2012-6613 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-6614](https://insights.sbomify.com/CVE-2012-6614/): Privilege escalation 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-6613 and fix it if it is affected.

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

## Sources

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

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