# CVE-2003-1578: Sun ONE (aka iPlanet) Web Server 4.1 through SP12 and 6.0 through SP5, when DNS resolution is enabled for client IP addresses, allows remote


- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Feb 2010
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-5mp7-vvfx-f7qm

## What is CVE-2003-1578?

CVE-2003-1578 is a medium-severity vulnerability in n/a, published on 5 Feb 2010. 

### Official description

Sun ONE (aka iPlanet) Web Server 4.1 through SP12 and 6.0 through SP5, when DNS resolution is enabled for client IP addresses, allows remote attackers to hide HTTP requests from the log-preview functionality by accompanying the requests with crafted DNS responses specifying a domain name beginning with a "format=" substring, related to an "Inverse Lookup Log Corruption (ILLC)" issue.

## Which versions are affected by CVE-2003-1578?

It affects 1 product.


Products: Sun One Web Server.

## How do I fix CVE-2003-1578?

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

## Is CVE-2003-1578 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-1589](https://insights.sbomify.com/CVE-2003-1589/): Denial of service in n/a (medium 5.0)
- [CVE-2003-1590](https://insights.sbomify.com/CVE-2003-1590/): Denial of service in n/a (medium 5.0)
- [CVE-2003-1126](https://insights.sbomify.com/CVE-2003-1126/): Denial of service in n/a (medium 5.0)
- [CVE-2003-1579](https://insights.sbomify.com/CVE-2003-1579/): Information disclosure in n/a (medium 4.3)
- [CVE-2005-2094](https://insights.sbomify.com/CVE-2005-2094/): Other in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-1578 and fix it if it is affected.

What it is: CVE-2003-1578 is a medium-severity vulnerability in n/a, published on 5 Feb 2010. 
Exploitation: There is no known exploitation of CVE-2003-1578 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-2003-1578/ (Markdown: https://insights.sbomify.com/CVE-2003-1578/index.md)
```

## Sources

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

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