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

> Remote FTP servers can execute arbitrary code on the client via a heap-based buffer overflow triggered by a long directory name in a LIST response.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Dec 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rj92-74hp-v94j

## What is CVE-2011-5012?

CVE-2011-5012 is a critical memory corruption vulnerability in n/a, published on 25 Dec 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Heap-based buffer overflow in the Reflection FTP Client (rftpcom.dll 7.2.0.106 and possibly other versions), as used in Attachmate Reflection 2008, Reflection 2011 R1 before 15.3.2.569 and R1 SP1 before, Reflection 2011 R2 before 15.4.1.327, Reflection Windows Client 7.2 SP1 before hotfix 7.2.1186, and Reflection 14.1 SP1 before 14.1.1.206, allows remote FTP servers to execute arbitrary code via a long directory name in a response to a LIST command.

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

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

It affects 5 products.


Products: Attachmate Reflection, Attachmate Reflection 2008, Attachmate Reflection 2008r1, Attachmate Reflection 2008r2, Attachmate Reflection 2011r1.

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

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

## Is CVE-2011-5012 being exploited?

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

Public exploit code:

- Attachmate Reflection FTP Client - Heap Overflow (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-5012 is a critical memory corruption vulnerability in n/a, published on 25 Dec 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-5012 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-5012/ (Markdown: https://insights.sbomify.com/CVE-2011-5012/index.md)
```

## Sources

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

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