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

> Local attackers can execute arbitrary code via format string vulnerabilities in the log function of SUS server software.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-mch4-wjp2-wj65

## What is CVE-2004-1469?

CVE-2004-1469 is a high-severity code injection vulnerability in n/a, published on 13 Feb 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Format string vulnerability in the log function in SUS 2.0.2, and other versions before 2.0.6, allows local users to execute arbitrary code via format string specifiers in a command line argument that is passed directly to syslog.

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

It affects 1 product.


Products: Peter D. Gray Sus.

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

No fix has been published for CVE-2004-1469 yet. Limit exposure of the affected software until one is available.

## Is CVE-2004-1469 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2004-1469 is a high-severity code injection vulnerability in n/a, published on 13 Feb 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-1469 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-1469/ (Markdown: https://insights.sbomify.com/CVE-2004-1469/index.md)
```

## Sources

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

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