# CVE-2022-28799: Open redirect in n/a

> Attackers can force the TikTok Android app to load arbitrary websites via crafted URLs, potentially leading to account takeover through JavaScript interfaces.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 May 2022
- **Updated:** 3 Aug 2024

## What is CVE-2022-28799?

CVE-2022-28799 is a high-severity vulnerability in n/a, published on 30 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The TikTok application before 23.7.3 for Android allows account takeover. A crafted URL (unvalidated deeplink) can force the com.zhiliaoapp.musically WebView to load an arbitrary website. This may allow an attacker to leverage an attached JavaScript interface for the takeover with one click.

Weakness: CWE-425 (Direct Request)

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

It affects 1 product.


Products: Tiktok Tiktok.

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

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

## Is CVE-2022-28799 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-14319](https://insights.sbomify.com/CVE-2019-14319/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-28799 is a high-severity vulnerability in n/a, published on 30 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-28799 in the wild and no public exploit code.

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

## Sources

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

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