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

> Remote attackers can execute arbitrary commands on Phicomm routers via the ping function's sendnum parameter.

- **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:** 7 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-pgmf-hqhq-5mq3

## What is CVE-2022-37779?

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

### Official description

Phicomm FIR151B A2, FIR302E A2, FIR300B A2, FIR303B A2 routers V3.0.1.17 were discovered to contain a remote command execution (RCE) vulnerability via the sendnum parameter of the ping function.

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

It affects 4 products.


Products: Phicomm Fir151b Firmware, Phicomm Fir300b Firmware, Phicomm Fir302e Firmware, Phicomm Fir303b Firmware.

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

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

## Is CVE-2022-37779 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-37777](https://insights.sbomify.com/CVE-2022-37777/): Command injection in n/a (high 7.2)
- [CVE-2022-37778](https://insights.sbomify.com/CVE-2022-37778/): Command injection in n/a (high 7.2)
- [CVE-2022-37780](https://insights.sbomify.com/CVE-2022-37780/): Command injection in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-37779 is a high-severity command injection vulnerability in n/a, published on 7 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-37779 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-37779/ (Markdown: https://insights.sbomify.com/CVE-2022-37779/index.md)
```

## Sources

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

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