# CVE-2004-0143: Memory corruption in n/a

> Remote attackers can cause a denial of service on Nokia 6310(i) phones by sending malformed Bluetooth OBEX messages, likely triggering buffer overflows.

- **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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Feb 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-pp95-7xxx-j2m4

## What is CVE-2004-0143?

CVE-2004-0143 is a medium-severity memory corruption vulnerability in n/a, published on 14 Feb 2004. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple vulnerabilities in Nokia 6310(i) Mobile phones allow remote attackers to cause a denial of service (reset) via malformed Bluetooth OBject EXchange (OBEX) messages, probably triggering buffer overflows.

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

It affects 1 product.


Products: Nokia 6310i.

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

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

## Is CVE-2004-0143 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0143 is a medium-severity memory corruption vulnerability in n/a, published on 14 Feb 2004. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-0143 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-0143/ (Markdown: https://insights.sbomify.com/CVE-2004-0143/index.md)
```

## Sources

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

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