# CVE-2024-20871: Security feature bypass in Samsung Keyboard

> Physical attackers can partially bypass factory reset protection in Samsung Keyboard, requiring an upgrade to the latest version.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L`)
- **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:** 7 May 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-7hfh-v896-8423

## What is CVE-2024-20871?

CVE-2024-20871 is a medium-severity vulnerability in Samsung Keyboard, published on 7 May 2024. 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

Improper authorization vulnerability in Samsung Keyboard prior to version One UI 5.1.1 allows physical attackers to partially bypass the factory reset protection.

## Which versions are affected by CVE-2024-20871?

It affects 1 product.


Products: Samsung One Ui.

## How do I fix CVE-2024-20871?

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

## Is CVE-2024-20871 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-20871 and fix it if it is affected.

What it is: CVE-2024-20871 is a medium-severity vulnerability in Samsung Keyboard, published on 7 May 2024. 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-2024-20871 in the wild and no public exploit code.

Affected product: Samsung Keyboard. 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-2024-20871/ (Markdown: https://insights.sbomify.com/CVE-2024-20871/index.md)
```

## Sources

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

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