# CVE-2022-29516: Command injection in IPCOM EX2 series, IPCOM EX series, IPCOM VE2 series, and IPCOM VA2/VE1 series

> Remote attackers can execute arbitrary OS commands on FUJITSU IPCOM network devices via the web console.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 18 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-fph2-ff2x-456c

## What is CVE-2022-29516?

CVE-2022-29516 is a critical command injection vulnerability in FUJITSU LIMITED IPCOM EX2 series, IPCOM EX series, IPCOM VE2 series, and IPCOM VA2/VE1 series, published on 18 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web console of FUJITSU Network IPCOM series (IPCOM EX2 IN(3200, 3500), IPCOM EX2 LB(1100, 3200, 3500), IPCOM EX2 SC(1100, 3200, 3500), IPCOM EX2 NW(1100, 3200, 3500), IPCOM EX2 DC, IPCOM EX2 DC, IPCOM EX IN(2300, 2500, 2700), IPCOM EX LB(1100, 1300, 2300, 2500, 2700), IPCOM EX SC(1100, 1300, 2300, 2500, 2700), and IPCOM EX NW(1100, 1300, 2300, 2500, 2700)) allows a remote attacker to execute an arbitrary OS command via unspecified vectors.

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

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

It affects 46 products.


Products: Fujitsu Ipcom Ex2 Dc 3200 Firmware, Fujitsu Ipcom Ex2 Dc 3500 Firmware, Fujitsu Ipcom Ex2 in 1100 Firmware, Fujitsu Ipcom Ex2 in 3200 Firmware, Fujitsu Ipcom Ex2 in 3500 Firmware, Fujitsu Ipcom Ex2 Lb 1100 Firmware, Fujitsu Ipcom Ex2 Lb 3200 Firmware, Fujitsu Ipcom Ex2 Lb 3500 Firmware, Fujitsu Ipcom Ex2 Nw 1100 Firmware, Fujitsu Ipcom Ex2 Nw 3200 Firmware, Fujitsu Ipcom Ex2 Nw 3500 Firmware, Fujitsu Ipcom Ex2 Sc 1100 Firmware, Fujitsu Ipcom Ex2 Sc 3200 Firmware, Fujitsu Ipcom Ex2 Sc 3500 Firmware, Fujitsu Ipcom Ex in 2300 Firmware, Fujitsu Ipcom Ex in 2500 Firmware, Fujitsu Ipcom Ex in 2700 Firmware, Fujitsu Ipcom Ex Lb 1100 Firmware, Fujitsu Ipcom Ex Lb 1300 Firmware, Fujitsu Ipcom Ex Lb 2300 Firmware and 26 more.

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

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

## Is CVE-2022-29516 being exploited?

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

## Other vulnerabilities in FUJITSU LIMITED IPCOM EX2 series, IPCOM EX series, IPCOM VE2 series, and IPCOM VA2/VE1 series

- [CVE-2024-39921](https://insights.sbomify.com/CVE-2024-39921/): Information disclosure in IPCOM EX2 Series (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29516 is a critical command injection vulnerability in FUJITSU LIMITED IPCOM EX2 series, IPCOM EX series, IPCOM VE2 series, and IPCOM VA2/VE1 series, published on 18 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-29516 in the wild and no public exploit code.

Affected product: FUJITSU LIMITED IPCOM EX2 series, IPCOM EX series, IPCOM VE2 series, and IPCOM VA2/VE1 series. 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-29516/ (Markdown: https://insights.sbomify.com/CVE-2022-29516/index.md)
```

## Sources

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

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