# CVE-2014-7859: Memory corruption in n/a

> Remote attackers can execute arbitrary code on D-Link network storage devices by sending malformed HTTP headers to the login manager.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 25 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-82v9-g947-fhvr

## What is CVE-2014-7859?

CVE-2014-7859 is a critical memory corruption vulnerability in n/a, published on 25 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in login_mgr.cgi in D-Link firmware DNR-320L and DNS-320LW before 1.04b08, DNR-322L before 2.10 build 03, DNR-326 before 2.10 build 03, and DNS-327L before 1.04b01 allows remote attackers to execute arbitrary code by crafting malformed "Host" and "Referer" header values.

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

## Which versions are affected by CVE-2014-7859?

It affects 5 products.


Products: D-Link Dnr-320l Firmware, D-Link Dnr-326 Firmware, D-Link Dns-320lw Firmware, D-Link Dns-322l Firmware, D-Link Dns-327l Firmware.

## How do I fix CVE-2014-7859?

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

## Is CVE-2014-7859 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-7859 and fix it if it is affected.

What it is: CVE-2014-7859 is a critical memory corruption vulnerability in n/a, published on 25 Aug 2017. 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-2014-7859 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-2014-7859/ (Markdown: https://insights.sbomify.com/CVE-2014-7859/index.md)
```

## Sources

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

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