# CVE-2022-41870: Command injection in n/a

> Attackers can execute arbitrary commands via modified service IDs during app upload in Innovaphone AP Manager, requiring an upgrade to mitigate.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2022
- **Updated:** 20 May 2025
- **Also known as:** GHSA-fm63-pfg2-7jrw

## What is CVE-2022-41870?

CVE-2022-41870 is a high-severity command injection vulnerability in n/a, published on 30 Sep 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

AP Manager in Innovaphone before 13r2 Service Release 17 allows command injection via a modified service ID during app upload.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 1 product.


Products: Innovaphone Innovaphone Firmware.

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

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

## Is CVE-2022-41870 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-41870 is a high-severity command injection vulnerability in n/a, published on 30 Sep 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-41870 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-41870/ (Markdown: https://insights.sbomify.com/CVE-2022-41870/index.md)
```

## Sources

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

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