# CVE-2022-44636: Security feature bypass in n/a

> Attackers can bypass microphone access controls on Samsung Smart TVs via Bluetooth spoofing during remote activation, requiring firmware updates.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Dec 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-63g5-x8w2-4383

## What is CVE-2022-44636?

CVE-2022-44636 is a medium-severity vulnerability in n/a, published on 13 Dec 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The Samsung TV (2021 and 2022 model) smart remote control allows attackers to enable microphone access via Bluetooth spoofing when a user is activating remote control by pressing a button. This is fixed in xxx72510, E9172511 for 2021 models, xxxA1000, 4x2A0200 for 2022 models.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2022-44636?

It affects 15 products.


Products: Samsung T-Ksu2eakuc Firmware, Samsung T-Ksu2edeuc Firmware, Samsung T-Ksu2euab Firmware, Samsung T-Nklakuc Firmware, Samsung T-Nkldeuc Firmware, Samsung T-Nkluabc Firmware, Samsung T-Nkm2akuc Firmware, Samsung T-Nkm2deuc Firmware, Samsung T-Nkm2uabc Firmware, Samsung T-Oscpakuc Firmware, Samsung T-Oscpdeuc Firmware, Samsung T-Oscpuabc Firmware, Samsung T-Ptmakuc Firmware, Samsung T-Ptmdeuc Firmware, Samsung T-Ptmuabc Firmware.

## How do I fix CVE-2022-44636?

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

## Is CVE-2022-44636 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-44636 and fix it if it is affected.

What it is: CVE-2022-44636 is a medium-severity vulnerability in n/a, published on 13 Dec 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-44636 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-2022-44636/ (Markdown: https://insights.sbomify.com/CVE-2022-44636/index.md)
```

## Sources

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

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