# CVE-2022-39872: Information disclosure in ShareLive

> An attacker can leak the MAC address of connected Bluetooth devices via improper Intent broadcasting in the Samsung ShareLive mobile application.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 7 Oct 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-gqh7-2v33-8jc4

## What is CVE-2022-39872?

CVE-2022-39872 is a medium-severity vulnerability in Samsung Mobile ShareLive, published on 7 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper restriction of broadcasting Intent in ShareLive prior to version 13.2.03.5 leaks MAC address of the connected Bluetooth device.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions), CWE-280 (Improper Handling of Insufficient Permissions or Privileges)

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

It affects 1 product.


Products: Samsung Sharelive.

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

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

## Is CVE-2022-39872 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-39872 is a medium-severity vulnerability in Samsung Mobile ShareLive, published on 7 Oct 2022. 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-2022-39872 in the wild and no public exploit code.

Affected product: Samsung Mobile ShareLive. 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-39872/ (Markdown: https://insights.sbomify.com/CVE-2022-39872/index.md)
```

## Sources

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

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