# CVE-2022-36834: Exposure of Sensitive Information vulnerability in Game Launcher prior to version 6.0.07 allows local attacker to access app data with user interaction.


- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-r57x-f9q6-74w3

## What is CVE-2022-36834?

CVE-2022-36834 is a low-severity vulnerability in Samsung Mobile Game Launcher, published on 5 Aug 2022. 

### Official description

Exposure of Sensitive Information vulnerability in Game Launcher prior to version 6.0.07 allows local attacker to access app data with user interaction.

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

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

It affects 1 product.


Products: Samsung Game Launcher.

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

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

## Is CVE-2022-36834 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36834 is a low-severity vulnerability in Samsung Mobile Game Launcher, published on 5 Aug 2022. 
Exploitation: There is no known exploitation of CVE-2022-36834 in the wild and no public exploit code.

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

## Sources

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

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