# CVE-2003-0412: Information disclosure in n/a

> Remote attackers can hide malicious activities because the server fails to log complete URIs for long HTTP requests.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-gj6g-3m57-qv5h

## What is CVE-2003-0412?

CVE-2003-0412 is a medium-severity vulnerability in n/a, published on 11 Jun 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sun ONE Application Server 7.0 for Windows 2000/XP does not log the complete URI of a long HTTP request, which could allow remote attackers to hide malicious activities.

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

It affects 1 product.


Products: Sun One Application Server.

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

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

## Is CVE-2003-0412 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-0387](https://insights.sbomify.com/CVE-2002-0387/): Memory corruption in n/a (high 7.5)
- [CVE-2003-0414](https://insights.sbomify.com/CVE-2003-0414/): Information disclosure in n/a (high 7.2)
- [CVE-2003-0413](https://insights.sbomify.com/CVE-2003-0413/): Cross-site scripting in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0412 is a medium-severity vulnerability in n/a, published on 11 Jun 2003. 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-2003-0412 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-0412/ (Markdown: https://insights.sbomify.com/CVE-2003-0412/index.md)
```

## Sources

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

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