# CVE-2004-0700: Other in n/a

> Remote attackers can execute arbitrary code via format string vulnerabilities in Apache mod_ssl HTTPS log handling.

- **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:** 21 Jul 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-mm6m-9rf6-5j2q

## What is CVE-2004-0700?

CVE-2004-0700 is a high-severity vulnerability in Gentoo Linux, published on 21 Jul 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 mod_proxy hook functions function in ssl_engine_log.c in mod_ssl before 2.8.19 for Apache before 1.3.31 may allow remote attackers to execute arbitrary messages via format string specifiers in certain log messages for HTTPS that are handled by the ssl_log function.

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

It affects 2 products.


Products: Gentoo Linux, Mod Ssl Mod Ssl.

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

Upgrade to a fixed version.

## Is CVE-2004-0700 being exploited?

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

## Other vulnerabilities in Gentoo Linux

- [CVE-2004-0914](https://insights.sbomify.com/CVE-2004-0914/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-1037](https://insights.sbomify.com/CVE-2004-1037/): Command injection in n/a (critical 10.0)
- [CVE-2004-1034](https://insights.sbomify.com/CVE-2004-1034/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0891](https://insights.sbomify.com/CVE-2004-0891/): Memory corruption in n/a (critical 10.0)
- [CVE-2002-1337](https://insights.sbomify.com/CVE-2002-1337/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0700 is a high-severity vulnerability in Gentoo Linux, published on 21 Jul 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-0700 in the wild and no public exploit code.

Affected product: Gentoo Linux. 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-0700/ (Markdown: https://insights.sbomify.com/CVE-2004-0700/index.md)
```

## Sources

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

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