# CVE-2006-0671: Memory corruption in n/a

> Remote attackers can cause denial of service on specific Sony Ericsson phones via malformed Bluetooth L2CAP packets.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **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:** 13 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-62cg-rmjp-wc9h

## What is CVE-2006-0671?

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

### Official description

Buffer overflow in Sony Ericsson K600i, V600i, W800i, and T68i cell phone allows remote attackers to cause a denial of service (reboot or shutdown) through a wireless Bluetooth connection via a malformed Logical Link Control and Adaptation Protocol (L2CAP) packet whose length field is less than the actual length of the packet.

## Which versions are affected by CVE-2006-0671?

It affects 4 products.


Products: Sony Ericsson K600i, Sony Ericsson T68i, Sony Ericsson V600i, Sony Ericsson W800i.

## How do I fix CVE-2006-0671?

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

## Is CVE-2006-0671 being exploited?

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

Public exploit code:

- Sony/Ericsson Bluetooth - Reset Display Denial of Service (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0671 and fix it if it is affected.

What it is: CVE-2006-0671 is a high-severity memory corruption vulnerability in n/a, published on 13 Feb 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0671 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-2006-0671/ (Markdown: https://insights.sbomify.com/CVE-2006-0671/index.md)
```

## Sources

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

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