# CVE-2009-0307: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script into the BES statistics page, requiring admin interaction to execute.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6v4f-j7rm-7833

## What is CVE-2009-0307?

CVE-2009-0307 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Apr 2009. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in the "Customize Statistics Page" (admin/statistics/ConfigureStatistics) in the MDS Connection Service in Research in Motion (RIM) BlackBerry Enterprise Server (BES) before 4.1.6 MR5 allows remote attackers to inject arbitrary web script or HTML via the (1) customDate, (2) interval, (3) lastCustomInterval, (4) lastIntervalLength, (5) nextCustomInterval, (6) nextIntervalLength, (7) action, (8) delIntervalIndex, (9) addStatIndex, (10) delStatIndex, and (11) referenceTime parameters.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Rim Blackberry Enterprise Server.

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

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

## Is CVE-2009-0307 being exploited?

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

Public exploit code:

- BlackBerry Enterprise Server 4.0/4.1 - MDS Connection Service Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-3483](https://insights.sbomify.com/CVE-2007-3483/): Misconfiguration in n/a (critical 10.0)
- [CVE-2010-2604](https://insights.sbomify.com/CVE-2010-2604/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-4778](https://insights.sbomify.com/CVE-2009-4778/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-2646](https://insights.sbomify.com/CVE-2009-2646/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-2643](https://insights.sbomify.com/CVE-2009-2643/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-0307 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Apr 2009. An attacker needs administrator access to exploit it, 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-2009-0307 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-2009-0307/ (Markdown: https://insights.sbomify.com/CVE-2009-0307/index.md)
```

## Sources

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

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