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

> Remote attackers can cause crashes or leak memory in Fetchmail via crafted NTLM responses when debug mode is enabled.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Dec 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-3482, GHSA-237f-j4ff-q54m, SUSE-SU-2016:0872-1

## What is CVE-2012-3482?

CVE-2012-3482 is a medium-severity memory corruption vulnerability in n/a, published on 21 Dec 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Fetchmail 5.0.8 through 6.3.21, when using NTLM authentication in debug mode, allows remote NTLM servers to (1) cause a denial of service (crash and delayed delivery of inbound mail) via a crafted NTLM response that triggers an out-of-bounds read in the base64 decoder, or (2) obtain sensitive information from memory via an NTLM Type 2 message with a crafted Target Name structure, which triggers an out-of-bounds read.

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `fetchmail` | SUSE:Linux Enterprise Desktop 11 SP4 | All versions | 6.3.8.90-13.20.21.1 |
| `fetchmail` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 6.3.8.90-13.20.21.1 |
| `fetchmail` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 6.3.8.90-13.20.21.1 |

Products: Fetchmail Fetchmail.

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

Upgrade to a fixed version.

## Is CVE-2012-3482 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-1009](https://insights.sbomify.com/CVE-2001-1009/): Integer overflow in n/a (critical 10.0)
- [CVE-2001-0101](https://insights.sbomify.com/CVE-2001-0101/): Other in n/a (critical 10.0)
- [CVE-2006-5867](https://insights.sbomify.com/CVE-2006-5867/): Weak cryptography in n/a (high 7.8)
- [CVE-2006-5974](https://insights.sbomify.com/CVE-2006-5974/): Null dereference in n/a (high 7.8)
- [CVE-2005-4348](https://insights.sbomify.com/CVE-2005-4348/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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