# CVE-2013-7005: Information disclosure in n/a

> Local attackers can read cleartext passwords from configuration files on D-Link routers, exposing sensitive credentials.

- **Severity:** Medium 4.9 (`AV:L/AC:L/Au:N/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-859c-w96r-58jw

## What is CVE-2013-7005?

CVE-2013-7005 is a medium-severity vulnerability in n/a, published on 19 Dec 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

D-Link DSR-150 with firmware before 1.08B44; DSR-150N with firmware before 1.05B64; DSR-250 and DSR-250N with firmware before 1.08B44; and DSR-500, DSR-500N, DSR-1000, and DSR-1000N with firmware before 1.08B77 stores account passwords in cleartext, which allows local users to obtain sensitive information by reading the Users[#]["Password"] fields in /tmp/teamf1.cfg.ascii.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 15 products.


Products: Dlink Dsr-1000, Dlink Dsr-1000 Firmware, Dlink Dsr-1000n, Dlink Dsr-1000n Firmware, Dlink Dsr-150, Dlink Dsr-150 Firmware, Dlink Dsr-150n, Dlink Dsr-150n Firmware, Dlink Dsr-250, Dlink Dsr-250 Firmware, Dlink Dsr-250n Firmware, Dlink Dsr-500, Dlink Dsr-500 Firmware, Dlink Dsr-500n, Dlink Dsr-500n Firmware.

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

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

## Is CVE-2013-7005 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-5946](https://insights.sbomify.com/CVE-2013-5946/): Command injection in n/a (critical 10.0)
- [CVE-2013-7004](https://insights.sbomify.com/CVE-2013-7004/): Hardcoded credentials in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-7005 is a medium-severity vulnerability in n/a, published on 19 Dec 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-7005 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-7005/ (Markdown: https://insights.sbomify.com/CVE-2013-7005/index.md)
```

## Sources

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

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