# CVE-2022-39893: Information disclosure in Galaxy Buds Pro Manager

> Local attackers with log access can extract device identifiers from Galaxy Buds Manager logs, exposing sensitive data.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Nov 2022
- **Updated:** 1 May 2025
- **Also known as:** GHSA-r576-65cc-q67j

## What is CVE-2022-39893?

CVE-2022-39893 is a low-severity vulnerability in Samsung Mobile Galaxy Buds Pro Manager, published on 9 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Sensitive information exposure vulnerability in FmmBaseModel in Galaxy Buds Pro Manage prior to version 4.1.22092751 allows local attackers with log access permission to get device identifier data through device log.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 1 product.


Products: Samsung Galaxy Buds Pro Manage.

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

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

## Is CVE-2022-39893 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-39893 is a low-severity vulnerability in Samsung Mobile Galaxy Buds Pro Manager, published on 9 Nov 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-39893 in the wild and no public exploit code.

Affected product: Samsung Mobile Galaxy Buds Pro Manager. 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-39893/ (Markdown: https://insights.sbomify.com/CVE-2022-39893/index.md)
```

## Sources

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

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