# CVE-2022-3183: Command injection in iBoot-PDU FW

> Attackers can execute arbitrary OS commands on Dataprobe iBoot-PDU devices due to unsanitized user input in a specific function.

- **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:** 21 Dec 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-985j-m96h-3qc5

## What is CVE-2022-3183?

CVE-2022-3183 is a critical command injection vulnerability in Dataprobe iBoot-PDU FW, published on 21 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dataprobe iBoot-PDU FW versions prior to 1.42.06162022 contain a vulnerability where a specific function does not sanitize the input provided by the user, which may expose the affected to an OS command injection vulnerability.

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

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

It affects 12 products.


Products: Dataprobe Iboot-Pdu4-N20 Firmware, Dataprobe Iboot-Pdu4a-N15 Firmware, Dataprobe Iboot-Pdu4a-N20 Firmware, Dataprobe Iboot-Pdu4sa-N15 Firmware, Dataprobe Iboot-Pdu4sa-N20 Firmware, Dataprobe Iboot-Pdu8a-2n15 Firmware, Dataprobe Iboot-Pdu8a-2n20 Firmware, Dataprobe Iboot-Pdu8a-N15 Firmware, Dataprobe Iboot-Pdu8a-N20 Firmware, Dataprobe Iboot-Pdu8sa-2n15 Firmware, Dataprobe Iboot-Pdu8sa-N15 Firmware, Dataprobe Iboot-Pdu8sa-N20 Firmware.

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

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

## Is CVE-2022-3183 being exploited?

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

## Other vulnerabilities in Dataprobe iBoot-PDU FW

- [CVE-2022-3184](https://insights.sbomify.com/CVE-2022-3184/): Path traversal in iBoot-PDU FW (critical 9.8)
- [CVE-2022-3186](https://insights.sbomify.com/CVE-2022-3186/): Missing authorization in iBoot-PDU FW (high 8.6)
- [CVE-2022-3185](https://insights.sbomify.com/CVE-2022-3185/): Information disclosure in iBoot-PDU FW (medium 5.3)
- [CVE-2022-3187](https://insights.sbomify.com/CVE-2022-3187/): Missing authorization in iBoot-PDU FW (medium 5.3)
- [CVE-2022-3188](https://insights.sbomify.com/CVE-2022-3188/): Missing authorization in iBoot-PDU FW (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3183 is a critical command injection vulnerability in Dataprobe iBoot-PDU FW, published on 21 Dec 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-3183 in the wild and no public exploit code.

Affected product: Dataprobe iBoot-PDU FW. 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-3183/ (Markdown: https://insights.sbomify.com/CVE-2022-3183/index.md)
```

## Sources

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

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