# CVE-2013-6027: Memory corruption in n/a

> Remote authenticated administrators can execute arbitrary commands via a stack-based buffer overflow in the diagnostic ping function.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-cjpj-cp59-mc73

## What is CVE-2013-6027?

CVE-2013-6027 is a high-severity memory corruption vulnerability in n/a, published on 19 Oct 2013. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Stack-based buffer overflow in the RuntimeDiagnosticPing function in /bin/webs on D-Link DIR-100 routers might allow remote authenticated administrators to execute arbitrary commands via a long set/runtime/diagnostic/pingIp parameter to Tools/tools_misc.xgi.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Dlink Dir-100.

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

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

## Is CVE-2013-6027 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6027 exists.

Public exploit code:

- D-Link / PLANEX COMMUNICATIONS - 'RuntimeDiagnosticPing()' Remote Stack Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-6027 is a high-severity memory corruption vulnerability in n/a, published on 19 Oct 2013. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6027 exists.

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-6027/ (Markdown: https://insights.sbomify.com/CVE-2013-6027/index.md)
```

## Sources

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

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