# CVE-2022-47028: Denial of service in n/a

> An attacker can cause a denial of service in Action Launcher for Android by injecting arbitrary data into the insert function.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 May 2023
- **Updated:** 14 Jan 2025
- **Also known as:** GHSA-r56f-m3qp-r2r5

## What is CVE-2022-47028?

CVE-2022-47028 is a medium-severity denial of service vulnerability in n/a, published on 30 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An issue discovered in Action Launcher for Android v50.5 allows an attacker to cause a denial of service via arbitary data injection to function insert.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 1 product.


Products: Actionlauncher Action Launcher.

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

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

## Is CVE-2022-47028 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-47028 exists.

## Other vulnerabilities in n/a

- [CVE-2022-47029](https://insights.sbomify.com/CVE-2022-47029/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-47028 is a medium-severity denial of service vulnerability in n/a, published on 30 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-47028 exists.

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-47028/ (Markdown: https://insights.sbomify.com/CVE-2022-47028/index.md)
```

## Sources

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

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