# CVE-2011-3992: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service via a buffer overflow in the SSH server of D-Link network devices.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Nov 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-64pp-ww3p-f3q4

## What is CVE-2011-3992?

CVE-2011-3992 is a critical memory corruption vulnerability in n/a, published on 3 Nov 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the SSH server functionality on the D-Link DES-3800 with firmware before 4.50B052, DWL-2100AP with firmware before 2.50RC548, and DWL-3200AP with firmware before 2.55RC549 allows remote attackers to execute arbitrary code or cause a denial of service via unspecified vectors.

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

## Which versions are affected by CVE-2011-3992?

It affects 6 products.


Products: Dlink Des-3800, Dlink Des-3800 Firmware, Dlink Dwl-2100ap, Dlink Dwl-2100ap Firmware, Dlink Dwl-3200ap, Dlink Dwl-3200ap Firmware.

## How do I fix CVE-2011-3992?

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

## Is CVE-2011-3992 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-5998](https://insights.sbomify.com/CVE-2013-5998/): Denial of service in n/a (high 7.8)
- [CVE-2013-5997](https://insights.sbomify.com/CVE-2013-5997/): Denial of service in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-3992 and fix it if it is affected.

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

## Sources

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

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