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

> Remote attackers can execute arbitrary code via format string vulnerabilities in GNU Anubis logging and error functions.

- **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:** No
- **Published:** 18 Mar 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-2v53-xxqh-55cg

## What is CVE-2004-0354?

CVE-2004-0354 is a critical memory corruption vulnerability in n/a, published on 18 Mar 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple format string vulnerabilities in GNU Anubis 3.6.0 through 3.6.2, 3.9.92 and 3.9.93 allow remote attackers to execute arbitrary code via format string specifiers in strings passed to (1) the info function in log.c, (2) the anubis_error function in errs.c, or (3) the ssl_error function in ssl.c.

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

It affects 1 product.


Products: Gnu Anubis.

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

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

## Is CVE-2004-0354 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-0354 exists.

Public exploit code:

- GNU Anubis 3.6.x/3.9.x - Multiple Format String Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0354 is a critical memory corruption vulnerability in n/a, published on 18 Mar 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-0354 exists.

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-0354/ (Markdown: https://insights.sbomify.com/CVE-2004-0354/index.md)
```

## Sources

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

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