# CVE-2022-36833: Privilege escalation in Game Optimizing Service

> A local attacker can execute hidden developer functions by changing the package name, leading to privilege escalation in Samsung's Game Optimizing Service.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/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:** 5 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-g6rv-f4m5-m22r

## What is CVE-2022-36833?

CVE-2022-36833 is a high-severity vulnerability in Samsung Mobile Game Optimizing Service, published on 5 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper Privilege Management vulnerability in Game Optimizing Service prior to versions 3.3.04.0 in Android 10, and 3.5.04.8 in Android 11 and above allows local attacker to execute hidden function for developer by changing package name.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Samsung Gameoptimizingservice.

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

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

## Is CVE-2022-36833 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36833 is a high-severity vulnerability in Samsung Mobile Game Optimizing Service, published on 5 Aug 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-36833 in the wild and no public exploit code.

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

## Sources

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

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