dbcve.org
Powerpanel ServerApplication · Cyberpower

CVE-2023-3261

HIGH · 7.2 CVSS v3.1 Published 2023-08-14
Fix available
A fix is available. Upgrade to 1.44.0804202 / 2.6.9 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Dataprobe iBoot PDU running firmware version 1.43.03312023 or earlier contains a buffer overflow vulnerability in the librta.so.0.0.0 library.Successful exploitation could cause denial of service or unexpected behavior with respect to all interactions relying on the targeted vulnerable binary, including the ability to log in via the web server.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Buffer overflow vulnerability in the librta.so.0.0.0 library of Dataprobe iBoot PDU firmware versions 1.43.03312023 and earlier allows memory corruption during input handling, potentially enabling denial of service or arbitrary behavior affecting all device interactions including web authentication.

MitigationUpdate firmware to a version newer than 1.43.03312023 when available; if no update exists, isolate the PDU behind a firewall and restrict administrative access to minimize attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Powerpanel ServerApplication
Affected:< 2.6.9
Iboot Pdu4a C10 FirmwareOperating system
Affected:< 1.44.0804202
Iboot Pdu4a C20 FirmwareOperating system
Affected:< 1.44.0804202
Iboot Pdu4a N15 FirmwareOperating system
Affected:< 1.44.0804202
Iboot Pdu4a N20 FirmwareOperating system
Affected:< 1.44.0804202
Iboot Pdu4 C20 FirmwareOperating system
Affected:< 1.44.0804202
Iboot Pdu4 N20 FirmwareOperating system
Affected:< 1.44.0804202
Iboot Pdu4sa C10 FirmwareOperating system
Affected:< 1.44.0804202

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the target is a Cyberpower Powerpanel Server
    Check the system or application inventory for Cyberpower Powerpanel Server installations; look for the Powerpanel Server service or process on the host
    Affected if Cyberpower Powerpanel Server version is found to be below 2.6.9
  2. Identify if the target is a Dataprobe iBoot PDU device
    Check network inventory or device documentation for Dataprobe iBoot PDU4, PDU4a, or PDU4sa model identifiers; access the device web interface or CLI to confirm the model
    Affected if A Dataprobe iBoot PDU model (PDU4, PDU4a, PDU4sa) is present on the network
  3. Check Cyberpower Powerpanel Server version
    On the host running Powerpanel Server, check the installed application version through the software's about page, installed programs list, or version metadata in the application directory
    Affected if The installed version is below 2.6.9
  4. Check Dataprobe iBoot PDU firmware version
    Log into the iBoot PDU web interface or CLI and navigate to the firmware or system information page to retrieve the current firmware version number
    Affected if The firmware version is 1.43.03312023 or earlier, or below 1.44.0804202 depending on the model
  5. Verify librta.so.0.0.0 library presence
    If filesystem access is available on the PDU or Powerpanel Server, search for the librta.so.0.0.0 library file in the application or firmware directories
    Affected if The librta.so.0.0.0 library exists on the device, indicating the vulnerable component is present

A user is affected if they have a Cyberpower Powerpanel Server below version 2.6.9 or a Dataprobe iBoot PDU (PDU4, PDU4a, PDU4sa) with firmware version 1.43.03312023 or earlier (or below 1.44.0804202), and the librta.so.0.0.0 library is present on the device.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.44.0804202 / 2.6.9 or later
Fixed in 1.44.08042022.6.9
Interim mitigation

Update firmware to a version newer than 1.43.03312023 when available; if no update exists, isolate the PDU behind a firewall and restrict administrative access to minimize attack surface.

Recommended fix High confidence

Firmware version 1.44.0804202 or later for iBoot PDU devices; Powerpanel Server version 2.6.9 or later

  1. 1. Identify the exact model of Dataprobe iBoot PDU or Powerpanel Server device from the affected product list
  2. 2. For iBoot PDU devices (Pdu4a C10, Pdu4a C20, Pdu4a N15, Pdu4a N20, Pdu4 C20, Pdu4 N20, Pdu4sa C10), download firmware version 1.44.0804202 or later from the Dataprobe support portal
  3. 3. For Powerpanel Server, upgrade to version 2.6.9 or later
  4. 4. Before applying the firmware upgrade, backup current configuration if possible
  5. 5. Apply the firmware upgrade following the vendor's standard upgrade procedure (typically via web interface or TFTP)
  6. 6. After upgrade, verify the device is functioning normally and the librta.so library has been updated
  7. 7. Confirm the web server login functionality is working as expected
Caveat firmware upgrades on PDU devices may temporarily interrupt power distribution - plan for maintenance window

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Powerpanel Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-3261 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-3261 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data