# CVE-2009-2575: Denial of service in n/a

> Remote attackers can crash the BlackBerry 8800 browser and consume memory by sending a large integer value for a Select object length.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:N/I:N/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:** 22 Jul 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qfrh-wqfx-qwvj

## What is CVE-2009-2575?

CVE-2009-2575 is a high-severity denial of service vulnerability in n/a, published on 22 Jul 2009. 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

The Research In Motion (RIM) BlackBerry 8800 allows remote attackers to cause a denial of service (memory consumption and browser crash) via a large integer value for the length property of a Select object, a related issue to CVE-2009-1692.

Weakness: CWE-399

## Which versions are affected by CVE-2009-2575?

It affects 1 product.


Products: Rim Blackberry 8800.

## How do I fix CVE-2009-2575?

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

## Is CVE-2009-2575 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-3944](https://insights.sbomify.com/CVE-2009-3944/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-2575 and fix it if it is affected.

What it is: CVE-2009-2575 is a high-severity denial of service vulnerability in n/a, published on 22 Jul 2009. 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-2009-2575 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-2009-2575/ (Markdown: https://insights.sbomify.com/CVE-2009-2575/index.md)
```

## Sources

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

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