# CVE-2006-1884: Other in n/a

> Unspecified vulnerability in Oracle Thesaurus Management System with unknown impact and attack vectors.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 20 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-383w-9x34-hwrc

## What is CVE-2006-1884?

CVE-2006-1884 is a critical vulnerability in Oracle Application Server, published on 20 Apr 2006. 

### Official description

Unspecified vulnerability in the Oracle Thesaurus Management System component in Oracle E-Business Suite and OPA 4.5.2 Applications has unknown impact and attack vectors, aka Vuln# OPA01.

## Which versions are affected by CVE-2006-1884?

It affects 12 products.


Products: Jdedwards Enterpriseone Tools, Oneworld Oneworld Tools, Oracle Application Server, Oracle Collaboration Suite, Oracle Collaboration Suite 10g Release 1, Oracle Database Server, Oracle Developer Suite, Oracle E-Business Suite, Oracle Enterprise Manager Grid Control, Oracle Peoplesoft Enterprise Tools, Oracle Pharmaceutical, Oracle Workflow.

## How do I fix CVE-2006-1884?

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

## Is CVE-2006-1884 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1884 and fix it if it is affected.

What it is: CVE-2006-1884 is a critical vulnerability in Oracle Application Server, published on 20 Apr 2006. 
Exploitation: There is no known exploitation of CVE-2006-1884 in the wild and no public exploit code.

Affected product: Oracle Application Server. 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-2006-1884/ (Markdown: https://insights.sbomify.com/CVE-2006-1884/index.md)
```

## Sources

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

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