# CVE-2005-2151: Memory corruption in n/a

> Attackers can cause memory corruption in Courier Mail Server via DNS failures during SPF record lookups, potentially leading to denial of service or code execution.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-2151, DSA-784-1, GHSA-j458-3qc3-3hff

## What is CVE-2005-2151?

CVE-2005-2151 is a medium-severity memory corruption vulnerability in n/a, published on 6 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

spf.c in Courier Mail Server does not properly handle DNS failures when looking up Sender Policy Framework (SPF) records, which could allow attackers to cause memory corruption.

## Which versions are affected by CVE-2005-2151?

It affects 1 product.


Products: Double Precision Incorporated Courier Mail Server.

## How do I fix CVE-2005-2151?

Apply the vendor's patch.

## Is CVE-2005-2151 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-3532](https://insights.sbomify.com/CVE-2005-3532/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2151 and fix it if it is affected.

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

## Sources

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

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