# CVE-2016-5681: Memory corruption in n/a

> Remote attackers can execute arbitrary code on D-Link routers via a stack-based buffer overflow in the login API using a long session cookie.

- **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:** 25 Aug 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-x7m8-97xv-fx44

## What is CVE-2016-5681?

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

### Official description

Stack-based buffer overflow in dws/api/Login on D-Link DIR-850L B1 2.07 before 2.07WWB05, DIR-817 Ax, DIR-818LW Bx before 2.05b03beta03, DIR-822 C1 3.01 before 3.01WWb02, DIR-823 A1 1.00 before 1.00WWb05, DIR-895L A1 1.11 before 1.11WWb04, DIR-890L A1 1.09 before 1.09b14, DIR-885L A1 1.11 before 1.11WWb07, DIR-880L A1 1.07 before 1.07WWb08, DIR-868L B1 2.03 before 2.03WWb01, and DIR-868L C1 3.00 before 3.00WWb01 devices allows remote attackers to execute arbitrary code via a long session cookie.

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

## Which versions are affected by CVE-2016-5681?

It affects 10 products.


Products: D-Link Dir-817l\(w\) Firmware, D-Link Dir-818l\(w\) Firmware, D-Link Dir-823 Firmware, D-Link Dir-850l Firmare, D-Link Dir-880l Firmware, D-Link Dir-885l Firmware, D-Link Dir-890l Firmware, D-Link Dir-895l Firmware, Dlink Dir-822 Firmware, Dlink Dir-868l Firmware.

## How do I fix CVE-2016-5681?

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

## Is CVE-2016-5681 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-5681 and fix it if it is affected.

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

## Sources

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

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