# CVE-2012-2210: Denial of service in n/a

> Remote attackers can crash Sony Bravia TVs or disrupt configuration by flooding them with TCP SYN 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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3p8j-6252-2pmw

## What is CVE-2012-2210?

CVE-2012-2210 is a high-severity denial of service vulnerability in n/a, published on 11 Apr 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Sony Bravia TV KDL-32CX525 allows remote attackers to cause a denial of service (configuration outage or device crash) via a flood of TCP SYN packets, as demonstrated by hping, a related issue to CVE-1999-0116.

Weakness: CWE-399

## Which versions are affected by CVE-2012-2210?

It affects 1 product.


Products: Sony Bravia Tv.

## How do I fix CVE-2012-2210?

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

## Is CVE-2012-2210 being exploited?

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

Public exploit code:

- Sony Bravia - Remote Denial of Service (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2210 and fix it if it is affected.

What it is: CVE-2012-2210 is a high-severity denial of service vulnerability in n/a, published on 11 Apr 2012. 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-2012-2210 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-2012-2210/ (Markdown: https://insights.sbomify.com/CVE-2012-2210/index.md)
```

## Sources

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

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