# CVE-2004-1597: Denial of service in n/a

> Remote attackers can cause denial of service and potential data corruption on BlackBerry devices by sending a calendar message with an overly long Location field.

- **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:** 20 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-h6j8-h5j9-864g

## What is CVE-2004-1597?

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

### Official description

RIM Blackberry 7230 running RIM Blackberry OS 3.7 SP1 allows remote attackers to cause a denial of service (device reboot and possibly data corruption) via a calendar message with a long Location field, which triggers a watchdog while the message is being stored.

## Which versions are affected by CVE-2004-1597?

It affects 1 product.


Products: Rim Blackberry.

## How do I fix CVE-2004-1597?

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

## Is CVE-2004-1597 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-1441](https://insights.sbomify.com/CVE-2007-1441/): Denial of service in n/a (medium 4.3)
- [CVE-2005-2343](https://insights.sbomify.com/CVE-2005-2343/): Denial of service in n/a (low 2.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1597 and fix it if it is affected.

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

## Sources

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

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