# CVE-2013-4706: Denial of service in n/a

> Authenticated remote attackers can cause a denial of service by triggering a reboot on D-Link Japan DWL-2100AP access points.

- **Severity:** Medium 6.3 (`AV:N/AC:M/Au:S/C:N/I:N/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:** 20 Sep 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-cfv8-9xwq-hwxw

## What is CVE-2013-4706?

CVE-2013-4706 is a medium-severity denial of service vulnerability in n/a, published on 20 Sep 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The SSH implementation on the D-Link Japan DWL-2100AP with firmware before R252JP-RC572 allows remote authenticated users to cause a denial of service (reboot) by leveraging login access.

Weakness: CWE-264

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

It affects 2 products.


Products: Dlink Dwl-2100ap, Dlink Dwl-2100ap Firmware.

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

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

## Is CVE-2013-4706 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-4706 is a medium-severity denial of service vulnerability in n/a, published on 20 Sep 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-4706 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-4706/ (Markdown: https://insights.sbomify.com/CVE-2013-4706/index.md)
```

## Sources

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

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