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

> Remote attackers can crash Samsung D6000 TVs by sending long strings to specific fields, causing a denial of service.

- **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:** 14 Aug 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pgh5-x82g-f7jf

## What is CVE-2012-4330?

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

### Official description

The Samsung D6000 TV and possibly other products allows remote attackers to cause a denial of service (crash) via a long string in certain fields, as demonstrated by the MAC address field, possibly a buffer overflow.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Samsung D6000 Firmware.

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

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

## Is CVE-2012-4330 being exploited?

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

Public exploit code:

- Samsung D6000 TV - Multiple Vulnerabilities (exploitdb)
- Samsung NET-i ware 1.37 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-4329](https://insights.sbomify.com/CVE-2012-4329/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-4330 is a high-severity denial of service vulnerability in n/a, published on 14 Aug 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-4330 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-2012-4330/ (Markdown: https://insights.sbomify.com/CVE-2012-4330/index.md)
```

## Sources

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

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