dbcve.org
PxOperating system · Raritan

CVE-2014-2955

HIGH · 10.0 CVSS v2.0 Published 2014-07-14
Fix available
A fix is available. Upgrade to after 1.5.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Raritan PX before 1.5.11 on DPXR20A-16 devices allows remote attackers to bypass authentication and execute arbitrary IPMI commands by using cipher suite 0 (aka cipher zero) and an arbitrary password.

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

Raritan PX PDUs before version 1.5.11 on DPXR20A-16 devices contain an IPMI authentication bypass vulnerability. Attackers exploit cipher suite 0 (cipher zero), a known weakness in IPMI protocol where this cipher allows authentication with any password, enabling full remote control of the PDU and execution of arbitrary IPMI commands.

MitigationUpgrade Raritan PX firmware to version 1.5.11 or later. Additionally, isolate IPMI interfaces on a separate management network, disable IPMI over LAN if unused, and restrict access to authorized administrative personnel.

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
PxOperating system
Affected:<= 1.5.8= 1.0= 1.0.4= 1.1= 1.1.6= 1.2= 1.2.5= 1.2.7= 1.3= 1.3.1= 1.3.5= 1.4.1
Dpxr20a 16Hardware / appliance
Affected:all versions

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 the Raritan PDU model
    Access the PDU web interface or check the physical device label to confirm the model is either a Raritan PX series or specifically a DPXR20A-16 unit.
    Affected if The device is a Raritan PX of any model or a DPXR20A-16 unit.
  2. Check the firmware version
    Log into the PDU web interface and navigate to the firmware or system information page. Alternatively, use the command line interface and run 'version' or 'show firmware' to retrieve the installed firmware version.
    Affected if The firmware version is 1.5.8 or lower, or matches any of these versions: 1.0, 1.0.4, 1.1, 1.1.6, 1.2, 1.2.5, 1.2.7, 1.3, 1.3.1, 1.3.5, or 1.4.1. For DPXR20A-16, all versions are affected.
  3. Verify IPMI over LAN is enabled
    Access the PDU web interface, go to the IPMI or network settings section, and check whether IPMI over LAN (also called IPMI over LAN access or BMC LAN access) is turned on. In CLI, use 'ipmi lan print' or similar command to check the IPMI interface status.
    Affected if IPMI over LAN is enabled, making the IPMI interface remotely accessible over the network.
  4. Confirm cipher 0 availability in IPMI configuration
    In the IPMI settings, locate the cipher suite configuration. Check if cipher suite 0 (cipher zero) is listed as available or enabled. Use the IPMI tool command 'ipmitool -I lanplus -H <device_ip> -u <user> -P <pass> cipher' to enumerate supported cipher suites if accessible.
    Affected if Cipher suite 0 is available or enabled in the IPMI configuration, which allows authentication bypass with any password.

If the device is a Raritan PX or DPXR20A-16 with an affected firmware version and IPMI over LAN is enabled with cipher 0 available, the environment is vulnerable to authentication bypass.

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 a release after 1.5.8
Interim mitigation

Upgrade Raritan PX firmware to version 1.5.11 or later. Additionally, isolate IPMI interfaces on a separate management network, disable IPMI over LAN if unused, and restrict access to authorized administrative personnel.

Recommended fix High confidence

Raritan PX firmware 1.5.11 or later

  1. Identify the current firmware version of the Raritan PX device via web interface or CLI
  2. Download firmware version 1.5.11 or later from Raritan's official support website
  3. Access the device's firmware upgrade interface (typically in Administration > Firmware Update)
  4. Upload and apply the firmware 1.5.11 or later following Raritan's standard upgrade procedure
  5. After reboot, verify the firmware has been updated successfully
  6. Test that authentication is working properly and cipher zero authentication bypass is no longer possible

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

Fix this in Px Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-2955 — 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-2014-2955 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