# CVE-2022-25824: Missing authorization in BixbyTouch

> Untrusted applications can load arbitrary URLs and local files in the BixbyTouch webview, potentially leading to code execution or data exposure.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 8 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-m4rr-r656-m8pj

## What is CVE-2022-25824?

CVE-2022-25824 is a medium-severity missing authorization vulnerability in Samsung Mobile BixbyTouch, published on 8 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper access control vulnerability in BixbyTouch prior to version 2.2.00.6 in China models allows untrusted applications to load arbitrary URL and local files in webview.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Samsung Bixby Touch.

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

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

## Is CVE-2022-25824 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-25824 is a medium-severity missing authorization vulnerability in Samsung Mobile BixbyTouch, published on 8 Mar 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-25824 in the wild and no public exploit code.

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

## Sources

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

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