# CVE-2006-2199: Security feature bypass in n/a

> Attackers can escape the Java sandbox and execute unauthorized code by tricking users into opening malicious OpenOffice documents.

- **Severity:** High 7.6 (`AV:N/AC:H/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 30 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m4r2-74mm-gqm4

## What is CVE-2006-2199?

CVE-2006-2199 is a high-severity vulnerability in n/a, published on 30 Jun 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Unspecified vulnerability in Java Applets in OpenOffice.org 1.1.x (aka StarOffice) up to 1.1.5 and 2.0.x before 2.0.3 allows user-assisted attackers to escape the Java sandbox and conduct unauthorized activities via certain applets in OpenOffice documents.

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

It affects 2 products.


Products: Openoffice Openoffice, Sun Staroffice.

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

Upgrade to a fixed version.

## Is CVE-2006-2199 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-4575](https://insights.sbomify.com/CVE-2007-4575/): Code injection in n/a (critical 9.3)
- [CVE-2007-0245](https://insights.sbomify.com/CVE-2007-0245/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-0238](https://insights.sbomify.com/CVE-2007-0238/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-0239](https://insights.sbomify.com/CVE-2007-0239/): Command injection in n/a (critical 9.3)
- [CVE-2006-5870](https://insights.sbomify.com/CVE-2006-5870/): Integer overflow in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2199 is a high-severity vulnerability in n/a, published on 30 Jun 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-2199 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-2006-2199/ (Markdown: https://insights.sbomify.com/CVE-2006-2199/index.md)
```

## Sources

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

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