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

> Remote attackers can obtain JSP source code by using uppercase file extensions, exposing sensitive application logic.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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-8ffw-58mq-48w9

## What is CVE-2003-0411?

CVE-2003-0411 is a high-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 allows remote attackers to obtain JSP source code via a request that uses the uppercase ".JSP" extension instead of the lowercase .jsp extension.

Weakness: CWE-178 (Improper Handling of Case Sensitivity)

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

It affects 1 product.


Products: Oracle Sun One Application Server.

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

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

## Is CVE-2003-0411 being exploited?

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

Public exploit code:

- Sun ONE Application Server 7.0 - Source Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0411 is a high-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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0411 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-2003-0411/ (Markdown: https://insights.sbomify.com/CVE-2003-0411/index.md)
```

## Sources

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

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