# CVE-2005-4813: Denial of service in n/a

> Remote attackers can cause a denial of service in Business Objects Crystal Reports Server by sending specific network traffic, potentially hanging the application.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 9 Oct 2006
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-xvx9-w67v-7f8g

## What is CVE-2005-4813?

CVE-2005-4813 is a medium-severity denial of service vulnerability in n/a, published on 9 Oct 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in Report Application Server (Crystalras.exe) before 11.0.0.1370, as used in Business Objects Crystal Reports XI, Crystal Reports Server XI, and BusinessObjects Enterprise XI, allows remote attackers to cause a denial of service (application hang) via certain network traffic, possibly involving multiple simultaneous TCP connections.

## Which versions are affected by CVE-2005-4813?

It affects 4 products.


Products: Businessobjects Crystal Enterprise Xi, Businessobjects Crystal Reports Server Xi, Businessobjects Crystal Reports Xi, Businessobjects Report Application Server.

## How do I fix CVE-2005-4813?

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

## Is CVE-2005-4813 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4813 and fix it if it is affected.

What it is: CVE-2005-4813 is a medium-severity denial of service vulnerability in n/a, published on 9 Oct 2006. 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-2005-4813 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-2005-4813/ (Markdown: https://insights.sbomify.com/CVE-2005-4813/index.md)
```

## Sources

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

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