# CVE-2022-4945: CVE-2022-4945

> Attackers with local file access can read plaintext cloud credentials, compromising other connected devices.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2023
- **Updated:** 16 Jan 2025
- **Also known as:** GHSA-gx4c-qrx5-9w6f

## What is CVE-2022-4945?

CVE-2022-4945 is a medium-severity vulnerability in Dataprobe, Inc. Dataprobe iBoot-PDU FW, published on 22 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Dataprobe cloud usernames and passwords are stored in plain text in a specific file. Any user able to read this specific file from the device could compromise other devices connected to the user's cloud.

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

It affects 22 products.


Products: Dataprobe Iboot-Pdu4-C20 Firmware, Dataprobe Iboot-Pdu4-N20 Firmware, Dataprobe Iboot-Pdu4a-C10 Firmware, Dataprobe Iboot-Pdu4a-C20 Firmware, Dataprobe Iboot-Pdu4a-N15 Firmware, Dataprobe Iboot-Pdu4a-N20 Firmware, Dataprobe Iboot-Pdu4sa-C10 Firmware, Dataprobe Iboot-Pdu4sa-C20 Firmware, Dataprobe Iboot-Pdu4sa-N15 Firmware, Dataprobe Iboot-Pdu4sa-N20 Firmware, Dataprobe Iboot-Pdu8a-2c10 Firmware, Dataprobe Iboot-Pdu8a-2c20 Firmware, Dataprobe Iboot-Pdu8a-2n15 Firmware, Dataprobe Iboot-Pdu8a-2n20 Firmware, Dataprobe Iboot-Pdu8a-C10 Firmware, Dataprobe Iboot-Pdu8a-C20 Firmware, Dataprobe Iboot-Pdu8a-N15 Firmware, Dataprobe Iboot-Pdu8a-N20 Firmware, Dataprobe Iboot-Pdu8sa-2n15 Firmware, Dataprobe Iboot-Pdu8sa-C10 Firmware and 2 more.

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

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

## Is CVE-2022-4945 being exploited?

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

## Other vulnerabilities in Dataprobe, Inc. Dataprobe iBoot-PDU FW

- [CVE-2023-3259](https://insights.sbomify.com/CVE-2023-3259/): Auth bypass in iBoot PDU (critical 9.8)
- [CVE-2022-47311](https://insights.sbomify.com/CVE-2022-47311/): CVE-2022-47311 (high 8.5)
- [CVE-2022-47320](https://insights.sbomify.com/CVE-2022-47320/): CVE-2022-47320 (high 8.1)
- [CVE-2023-3263](https://insights.sbomify.com/CVE-2023-3263/): Auth bypass in iBoot PDU (high 7.5)
- [CVE-2022-46738](https://insights.sbomify.com/CVE-2022-46738/): CVE-2022-46738 (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4945 is a medium-severity vulnerability in Dataprobe, Inc. Dataprobe iBoot-PDU FW, published on 22 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-4945 in the wild and no public exploit code.

Affected product: Dataprobe, Inc. 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-4945/ (Markdown: https://insights.sbomify.com/CVE-2022-4945/index.md)
```

## Sources

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

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