# CVE-2012-4409: Memory corruption in n/a

> A stack-based buffer overflow in mcrypt allows remote attackers to execute arbitrary code via a crafted encrypted file, requiring user interaction to open the file.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** Yes
- **Published:** 21 Nov 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-4409, GHSA-x2pj-g5q5-wh2x

## What is CVE-2012-4409?

CVE-2012-4409 is a medium-severity memory corruption vulnerability in n/a, published on 21 Nov 2012. 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 check_file_head function in extra.c in mcrypt 2.6.8 and earlier allows user-assisted remote attackers to execute arbitrary code via an encrypted file with a crafted header containing long salt data that is not properly handled during decryption.

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

## Which versions are affected by CVE-2012-4409?

It affects 1 product.


Products: Mcrypt Mcrypt.

## How do I fix CVE-2012-4409?

Upgrade to a fixed version.

## Is CVE-2012-4409 being exploited?

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

Public exploit code:

- mcrypt 2.5.8 - Local Stack Overflow (exploitdb)
- mcrypt 2.6.8 - Stack Buffer Overflow (PoC) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-4426](https://insights.sbomify.com/CVE-2012-4426/): Other in n/a (medium 6.8)
- [CVE-2012-4527](https://insights.sbomify.com/CVE-2012-4527/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-4409 and fix it if it is affected.

What it is: CVE-2012-4409 is a medium-severity memory corruption vulnerability in n/a, published on 21 Nov 2012. 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-2012-4409 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-2012-4409/ (Markdown: https://insights.sbomify.com/CVE-2012-4409/index.md)
```

## Sources

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

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