# CVE-2022-36839: SQL injection in Samsung Checkout

> Attackers can exploit SQL injection in Samsung Checkout to access In-App Purchase information.

- **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:** 5 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-gwhx-pr3x-qrfm

## What is CVE-2022-36839?

CVE-2022-36839 is a medium-severity SQL injection vulnerability in Samsung Checkout, 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

SQL injection vulnerability via IAPService in Samsung Checkout prior to version 5.0.53.1 allows attackers to access IAP information.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Samsung Checkout.

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

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

## Is CVE-2022-36839 being exploited?

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

## Other vulnerabilities in Samsung Checkout

- [CVE-2022-39878](https://insights.sbomify.com/CVE-2022-39878/): Information disclosure in Samsung Checkout (medium 4.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36839 is a medium-severity SQL injection vulnerability in Samsung Checkout, 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-36839 in the wild and no public exploit code.

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

## Sources

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

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