# CVE-2004-2571: Memory corruption in n/a

> Remote attackers can execute arbitrary code via buffer overflows in EnderUNIX isoqlog mail log parsing functions.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** Not needed
- **Fix available:** Yes
- **Published:** 22 Nov 2005
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-2571, GHSA-49h7-mvgr-p5p6

## What is CVE-2004-2571?

CVE-2004-2571 is a high-severity memory corruption vulnerability in n/a, published on 22 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple buffer overflows in EnderUNIX isoqlog 2.1.1 allow remote attackers to execute arbitrary code via the (1) parseQmailFromBytesLine, (2) parseQmailToRemoteLine, (3) parseQmailToLocalLine, (4) parseSendmailFromBytesLine, (5) parseSendmailToLine, (6) parseEximFromBytesLine, and (7) parseEximToLine functions in Parser.c; allow local users to execute arbitrary code via the (8) lowercase and (9) check_syslog_date functions in Parser.c, and (10) unspecified functions in Dir.c; and allow unspecified attackers to execute arbitrary code via the (11) loadconfig and (12) removespaces functions in loadconfig.c, the (13) loadLang function in LangCfg.c, and (14) unspecified functions in Html.c.

## Which versions are affected by CVE-2004-2571?

It affects 1 product.


Products: Enderunix Isoqlog.

## How do I fix CVE-2004-2571?

Upgrade to a fixed version.

## Is CVE-2004-2571 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2571 and fix it if it is affected.

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

## Sources

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

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