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

> A stack-based buffer overflow in Free Download Manager allows remote attackers to execute arbitrary code via a long file name when the user deletes it from the queue.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** 18 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f5vv-v37r-r859

## What is CVE-2014-2087?

CVE-2014-2087 is a critical memory corruption vulnerability in n/a, published on 18 Mar 2014. 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

Stack-based buffer overflow in the CDownloads_Deleted::UpdateDownload function in Downloads_Deleted.cpp in Free Download Manager 3.9.3 build 1360, 3.8 build 1173, 3.0 build 852, and earlier allows user-assisted remote attackers to execute arbitrary code via a long file name, which is then deleted from the download queue by the user.

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

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

It affects 1 product.


Products: Freedownloadmanager Free Download Manager.

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

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

## Is CVE-2014-2087 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-2087 exists.

Public exploit code:

- Free Download Manager - Stack Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-0998](https://insights.sbomify.com/CVE-2010-0998/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-0999](https://insights.sbomify.com/CVE-2010-0999/): Path traversal in n/a (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2087 is a critical memory corruption vulnerability in n/a, published on 18 Mar 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-2087 exists.

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-2087/ (Markdown: https://insights.sbomify.com/CVE-2014-2087/index.md)
```

## Sources

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

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