# CVE-2019-6258: Memory corruption in n/a

> A buffer overflow in D-Link DIR-822 routers allows remote attackers to execute arbitrary code via a crafted HNAP message.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2jv7-c5x2-xf95

## What is CVE-2019-6258?

CVE-2019-6258 is a critical memory corruption vulnerability in n/a, published on 18 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

D-Link DIR-822 Rev.Bx devices with firmware v.202KRb06 and older allow a buffer overflow via long MacAddress data in a /HNAP1/SetClientInfo HNAP protocol message, which is mishandled in /usr/sbin/udhcpd during reading of the /var/servd/LAN-1-udhcpd.conf file.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2019-6258?

It affects 1 product.


Products: D-Link Dir-822 Firmware.

## How do I fix CVE-2019-6258?

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

## Is CVE-2019-6258 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-19989](https://insights.sbomify.com/CVE-2018-19989/): Command injection in n/a (critical 9.8)
- [CVE-2018-19990](https://insights.sbomify.com/CVE-2018-19990/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6258 and fix it if it is affected.

What it is: CVE-2019-6258 is a critical memory corruption vulnerability in n/a, published on 18 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-6258 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-2019-6258/ (Markdown: https://insights.sbomify.com/CVE-2019-6258/index.md)
```

## Sources

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

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