# CVE-2015-5729: Weak cryptography in n/a

> Weak WPA2 keys in Samsung Smart TV Soft AP allow remote attackers to bypass authentication and access sensitive data via brute-force.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Mar 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-q9vm-xr73-4r75

## What is CVE-2015-5729?

CVE-2015-5729 is a critical vulnerability in n/a, published on 23 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Soft Access Point (AP) feature in Samsung Smart TVs X10P, X12, X14H, X14J, and NT14U and Xpress M288OFW printers generate weak WPA2 PSK keys, which makes it easier for remote attackers to obtain sensitive information or bypass authentication via a brute-force attack.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2015-5729?

It affects 6 products.


Products: Samsung M288ofw Firmware, Samsung Nt14u Firmware, Samsung X10p Firmware, Samsung X12 Firmware, Samsung X14h Firmware, Samsung X14j Firmware.

## How do I fix CVE-2015-5729?

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

## Is CVE-2015-5729 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-5729 and fix it if it is affected.

What it is: CVE-2015-5729 is a critical vulnerability in n/a, published on 23 Mar 2017. 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-2015-5729 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-2015-5729/ (Markdown: https://insights.sbomify.com/CVE-2015-5729/index.md)
```

## Sources

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

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