# CVE-2002-1639: Information disclosure in n/a

> Remote attackers can obtain sensitive version and host information by sending specific requests to the UiServlet in Oracle Configurator.

- **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:** No
- **Published:** 28 Mar 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-mqr3-hx46-j2rf

## What is CVE-2002-1639?

CVE-2002-1639 is a high-severity vulnerability in n/a, published on 28 Mar 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Oracle Configurator before 11.5.7.17.32 and 11.5.6.16.53 allows remote attackers to obtain sensitive information via a request to the oracle.apps.cz.servlet.UiServlet servlet with the test parameter set to "version" or "host".

## Which versions are affected by CVE-2002-1639?

It affects 1 product.


Products: Oracle Configurator.

## How do I fix CVE-2002-1639?

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

## Is CVE-2002-1639 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-61884](https://insights.sbomify.com/CVE-2025-61884/): Oracle E-Business Suite Server-Side Request Forgery (SSRF) (high 7.5, exploited in the wild)
- [CVE-2021-2078](https://insights.sbomify.com/CVE-2021-2078/): Cross-site scripting in Configurator (high 8.2)
- [CVE-2021-2079](https://insights.sbomify.com/CVE-2021-2079/): Cross-site scripting in Configurator (high 8.2)
- [CVE-2021-2080](https://insights.sbomify.com/CVE-2021-2080/): Cross-site scripting in Configurator (high 8.2)
- [CVE-2020-14669](https://insights.sbomify.com/CVE-2020-14669/): Cross-site scripting in Configurator (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1639 and fix it if it is affected.

What it is: CVE-2002-1639 is a high-severity vulnerability in n/a, published on 28 Mar 2005. 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-2002-1639 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-2002-1639/ (Markdown: https://insights.sbomify.com/CVE-2002-1639/index.md)
```

## Sources

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

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