# CVE-2021-25406: Information disclosure in Gear S Plugin

> Untrusted applications can access connected Bluetooth device information via the Samsung Gear S Plugin, exposing sensitive data to malicious apps.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-3px8-7pj4-m3r5

## What is CVE-2021-25406?

CVE-2021-25406 is a medium-severity vulnerability in Samsung Mobile Gear S Plugin, published on 11 Jun 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Information exposure vulnerability in Gear S Plugin prior to version 2.2.05.20122441 allows unstrusted applications to access connected BT device information.

Weakness: CWE-863 (Incorrect Authorization), CWE-922 (Insecure Storage of Sensitive Information)

## Which versions are affected by CVE-2021-25406?

It affects 1 product.


Products: Samsung Gear S.

## How do I fix CVE-2021-25406?

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

## Is CVE-2021-25406 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-25406 and fix it if it is affected.

What it is: CVE-2021-25406 is a medium-severity vulnerability in Samsung Mobile Gear S Plugin, published on 11 Jun 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-25406 in the wild and no public exploit code.

Affected product: Samsung Mobile Gear S Plugin. 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-2021-25406/ (Markdown: https://insights.sbomify.com/CVE-2021-25406/index.md)
```

## Sources

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

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