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

> Attackers can inject commands via ping and traceroute tools to read arbitrary files on the GL.iNet GoodCloud IoT management system.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2022
- **Updated:** 7 May 2025
- **Also known as:** GHSA-4cv7-c8cq-mg9f

## What is CVE-2022-42055?

CVE-2022-42055 is a medium-severity command injection vulnerability in n/a, published on 27 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple command injection vulnerabilities in GL.iNet GoodCloud IoT Device Management System Version 1.00.220412.00 via the ping and traceroute tools allow attackers to read arbitrary files on the system.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Gl-Inet Goodcloud.

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

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

## Is CVE-2022-42055 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-44211](https://insights.sbomify.com/CVE-2022-44211/): Missing authorization in n/a (high 7.4)
- [CVE-2022-44212](https://insights.sbomify.com/CVE-2022-44212/): Missing authorization in n/a (medium 5.9)
- [CVE-2022-42054](https://insights.sbomify.com/CVE-2022-42054/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-42055 is a medium-severity command injection vulnerability in n/a, published on 27 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-42055 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-42055/ (Markdown: https://insights.sbomify.com/CVE-2022-42055/index.md)
```

## Sources

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

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