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

> Attackers can crash the Nokia 9500 vCard viewer by sending a vCard with an excessively long Name field, requiring user interaction to view.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Jun 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cp24-qvpw-wmp5

## What is CVE-2005-1801?

CVE-2005-1801 is a low-severity denial of service vulnerability in n/a, published on 1 Jun 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The vCard viewer in Nokia 9500 allows attackers to cause a denial of service (crash) via a vCard with a long Name field, which causes the crash when the user views it.

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

It affects 1 product.


Products: Nokia 9500.

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

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

## Is CVE-2005-1801 being exploited?

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

Public exploit code:

- Nokia 9500 - vCard Viewer Remote Denial of Service (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1801 is a low-severity denial of service vulnerability in n/a, published on 1 Jun 2005. It can only be exploited from the same machine or local network, 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-2005-1801 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-2005-1801/ (Markdown: https://insights.sbomify.com/CVE-2005-1801/index.md)
```

## Sources

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

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