# CVE-2004-2763: Cross-site scripting in n/a

> Attackers can steal sensitive information via cross-site tracing if the web server allows TRACE requests and the application is vulnerable to XSS.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Jun 2009
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-79p6-hxp5-mfcw

## What is CVE-2004-2763?

CVE-2004-2763 is a medium-severity cross-site scripting vulnerability in n/a, published on 1 Jun 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The default configuration of Sun ONE/iPlanet Web Server 4.1 SP1 through SP12 and 6.0 SP1 through SP5 responds to the HTTP TRACE request, which can allow remote attackers to steal information using cross-site tracing (XST) attacks in applications that are vulnerable to cross-site scripting.

Weakness: CWE-16

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

It affects 2 products.


Products: Sun Iplanet Web Server, Sun One Web Server.

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

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

## Is CVE-2004-2763 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0183](https://insights.sbomify.com/CVE-2007-0183/): Cross-site scripting in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-2763 is a medium-severity cross-site scripting vulnerability in n/a, published on 1 Jun 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2004-2763 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-2004-2763/ (Markdown: https://insights.sbomify.com/CVE-2004-2763/index.md)
```

## Sources

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

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