# CVE-2006-6133: Memory corruption in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a crafted RPT file in Visual Studio Crystal Reports.

- **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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j25h-8cx4-j53h

## What is CVE-2006-6133?

CVE-2006-6133 is a high-severity memory corruption vulnerability in n/a, published on 28 Nov 2006. 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

Stack-based buffer overflow in Visual Studio Crystal Reports for Microsoft Visual Studio .NET 2002 and 2002 SP1, .NET 2003 and 2003 SP1, and 2005 and 2005 SP1 (formerly Business Objects Crystal Reports XI Professional) allows user-assisted remote attackers to execute arbitrary code via a crafted RPT file.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 2 products.


Products: Businessobjects Crystal Reports Xi, Microsoft Visual Studio .Net.

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

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

## Is CVE-2006-6133 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6133 exists.

Public exploit code:

- Business Objects Crystal Reports XI Professional - File Handling Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-0379](https://insights.sbomify.com/CVE-2008-0379/): Race condition in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6133 is a high-severity memory corruption vulnerability in n/a, published on 28 Nov 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6133 exists.

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-6133/ (Markdown: https://insights.sbomify.com/CVE-2006-6133/index.md)
```

## Sources

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

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