# CVE-2006-6988: Information disclosure in n/a

> Remote attackers can access restricted cross-domain information in Slim Browser via crafted object tags, requiring user interaction to view the malicious content.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/I:N/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:** 9 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-26cp-jrgm-wmvv

## What is CVE-2006-6988?

CVE-2006-6988 is a high-severity vulnerability in n/a, published on 9 Feb 2007. 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

Cross-domain vulnerability in Slim Browser 4.07 build 100 allows remote attackers to access restricted information from other domains via an object tag with a data parameter that references a link on the attacker's originating site that specifies a Location HTTP header that references the target site, which then makes that content available through the outerHTML attribute of the object, a similar vulnerability to CVE-2006-3280.

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

It affects 1 product.


Products: Flashpeak Slim Browser.

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

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

## Is CVE-2006-6988 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6988 is a high-severity vulnerability in n/a, published on 9 Feb 2007. 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-2006-6988 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-6988/ (Markdown: https://insights.sbomify.com/CVE-2006-6988/index.md)
```

## Sources

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

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