# CVE-2023-3259: Auth bypass in iBoot PDU

> Attackers can bypass authentication by manipulating a cookie to gain admin privileges, allowing power control and data access on Dataprobe iBoot PDUs.

- **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:** 14 Aug 2023
- **Updated:** 9 Oct 2024
- **Also known as:** GHSA-qxx8-22p6-c299

## What is CVE-2023-3259?

CVE-2023-3259 is a critical authentication bypass vulnerability in Dataprobe iBoot PDU, published on 14 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Dataprobe iBoot PDU running firmware version 1.43.03312023 or earlier is vulnerable to authentication bypass. By manipulating the IP address field in the "iBootPduSiteAuth" cookie, a malicious agent can direct the device to connect to a rouge database.Successful exploitation allows the malicious agent to take actions with administrator privileges including, but not limited to, manipulating power levels, modifying user accounts, and exporting confidential user information

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2023-3259?

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-2023-3259?

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

## Is CVE-2023-3259 being exploited?

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

## Other vulnerabilities in Dataprobe iBoot PDU

- [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)
- [CVE-2023-3262](https://insights.sbomify.com/CVE-2023-3262/): Hardcoded credentials in iBoot PDU (medium 6.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3259 and fix it if it is affected.

What it is: CVE-2023-3259 is a critical authentication bypass vulnerability in Dataprobe iBoot PDU, published on 14 Aug 2023. 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-2023-3259 in the wild and no public exploit code.

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

## Sources

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

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