# CVE-2021-26709: Memory corruption in n/a

> Unauthenticated remote attackers can execute arbitrary code and take over the device via stack-based buffer overflows in the login parameters.

- **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:** 7 Apr 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-rpch-r72m-hrcf

## What is CVE-2021-26709?

CVE-2021-26709 is a critical memory corruption vulnerability in n/a, published on 7 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

D-Link DSL-320B-D1 devices through EU_1.25 are prone to multiple Stack-Based Buffer Overflows that allow unauthenticated remote attackers to take over a device via the login.xgi user and pass parameters. NOTE: This vulnerability only affects products that are no longer supported by the maintainer

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2021-26709?

It affects 1 product.


Products: D-Link Dsl-320b-D1.

## How do I fix CVE-2021-26709?

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

## Is CVE-2021-26709 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-26709 and fix it if it is affected.

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

## Sources

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

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