dbcve.org
Data Protector ExpressApplication · Hp

CVE-2012-0124

HIGH · 10.0 CVSS v2.0 Published 2012-03-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
Unspecified vulnerability in HP Data Protector Express (aka DPX) 5.0.00 before build 59287 and 6.0.00 before build 11974 allows remote attackers to execute arbitrary code or cause a denial of service via unknown vectors.

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 · moderate confidence

HP Data Protector Express versions 5.0.00 before build 59287 and 6.0.00 before build 11974 contain an unspecified vulnerability allowing remote attackers to execute arbitrary code or cause denial of service. The CVSS 10 score indicates network-exploitable code execution without authentication.

MitigationUpgrade HP Data Protector Express to build 59287 (5.0.x series) or build 11974 (6.0.x series) or later. If upgrading is not immediately possible, restrict network access to DPX services and monitor for indicators of compromise.

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
Data Protector ExpressApplication
Affected:= 5.0= 6.0

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 HP Data Protector Express installation
    Locate the HP Data Protector Express installation directory, typically under C:\Program Files\HP\Data Protector Express or /opt/HP/Data Protector Express on Unix systems. Check for the presence of the DPExpress or similar executable files.
    Affected if HP Data Protector Express software is installed on the system
  2. Determine installed version and build number
    Open the application or check version information through the Windows Add/Remove Programs panel, or run the executable with a version flag such as 'dpaconfig -version' or look for a version.txt file in the installation directory.
    Affected if The installed version is 5.0.x with build number below 59287, or 6.0.x with build number below 11974, or if the build number cannot be determined and the version matches 5.0 or 6.0
  3. Verify service is network accessible
    Check if the HP Data Protector Express services are listening on network ports (typically TCP ports 2000 series for the cell manager). Use netstat or similar network utility to confirm open listening ports.
    Affected if The DP Express services are exposed to the network and the version/build is vulnerable
  4. Confirm authentication configuration
    Review the security settings within the DP Express console or configuration files to verify whether remote unauthenticated access is permitted.
    Affected if Remote unauthenticated access is allowed and the version/build falls within the affected range

A user is affected if HP Data Protector Express version 5.0.x with build below 59287 or version 6.0.x with build below 11974 is installed and network-accessible without being behind restricted access controls.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade HP Data Protector Express to build 59287 (5.0.x series) or build 11974 (6.0.x series) or later. If upgrading is not immediately possible, restrict network access to DPX services and monitor for indicators of compromise.

Recommended fix Moderate confidence

HP Data Protector Express 5.0.00 build 59287 or later; HP Data Protector Express 6.0.00 build 11974 or later

  1. 1. Identify the current installed build of HP Data Protector Express by checking the application version information
  2. 2. For Data Protector Express 5.0.00: Upgrade to build 59287 or later
  3. 3. For Data Protector Express 6.0.00: Upgrade to build 11974 or later
  4. 4. Obtain the updated installation package from HP/Oracle (now the product owner) or your licensed vendor
  5. 5. Back up the current Data Protector Express configuration and database before upgrading
  6. 6. Apply the upgrade following the vendor's standard upgrade procedure
  7. 7. Verify the new build version is correctly installed after upgrade
  8. 8. Test critical backup/restore operations to confirm normal functionality
Caveat Major version upgrades may introduce compatibility changes with existing backup clients or require license reactivation; ensure compatibility checks before production deployment

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

Fix this in Data Protector Express Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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