# CVE-2004-0450: Code injection in n/a

> Attackers can execute arbitrary code via format string vulnerabilities in log files monitored by log2mail.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jun 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DSA-513, GHSA-rxgx-f27q-r49h

## What is CVE-2004-0450?

CVE-2004-0450 is a critical code injection vulnerability in n/a, published on 8 Jun 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Format string vulnerability in the printlog function in log2mail before 0.2.5.2 allows local users or remote attackers to execute arbitrary code via format string specifiers in a logfile monitored by log2mail.

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

It affects 1 product.


Products: Log2mail Log2mail.

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

Upgrade to a fixed version.

## Is CVE-2004-0450 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1251](https://insights.sbomify.com/CVE-2002-1251/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0450 is a critical code injection vulnerability in n/a, published on 8 Jun 2004. 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-0450 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-0450/ (Markdown: https://insights.sbomify.com/CVE-2004-0450/index.md)
```

## Sources

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

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