# CVE-2022-36878: Information disclosure in Find My Mobile

> A local attacker can access sensitive IMEI information via logs in the Samsung Find My Mobile application.

- **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 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-fhph-g84c-4j7p

## What is CVE-2022-36878?

CVE-2022-36878 is a low-severity vulnerability in Samsung Mobile Find My Mobile, published on 9 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Exposure of Sensitive Information in Find My Mobile prior to version 7.2.25.14 allows local attacker to access IMEI via log.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Samsung Find My Mobile.

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

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

## Is CVE-2022-36878 being exploited?

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

## Other vulnerabilities in Samsung Mobile Find My Mobile

- [CVE-2023-42571](https://insights.sbomify.com/CVE-2023-42571/): Auth bypass in Find My Mobile (high 7.6)
- [CVE-2022-33707](https://insights.sbomify.com/CVE-2022-33707/): Information disclosure in FindMyMobile (medium 5.3)
- [CVE-2022-30741](https://insights.sbomify.com/CVE-2022-30741/): Information disclosure in Find My Mobile (low 3.3)
- [CVE-2022-30742](https://insights.sbomify.com/CVE-2022-30742/): Information disclosure in Find My Mobile (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36878 is a low-severity vulnerability in Samsung Mobile Find My Mobile, published on 9 Sep 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-36878 in the wild and no public exploit code.

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

## Sources

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

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