dbcve.org
Data Protector ExpressApplication · Hp

CVE-2012-0123

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
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, aka ZDI-CAN-1498.

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 score of 10 indicates critical severity with network-exploitable, unauthenticated attack vector and complete impact on confidentiality, integrity, and availability.

MitigationUpdate HP Data Protector Express to build 59287 or later for version 5.0.00, and build 11974 or later for version 6.0.00. If patching is not immediately feasible, 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. Verify HP Data Protector Express is installed
    Check installed programs or services list for 'HP Data Protector Express' or 'DPX' entries
    Affected if HP Data Protector Express is not installed - not affected
  2. Identify the installed version
    Use the product's about dialog, version info in the installation directory, or check the installed program details to determine if version 5.0 or 6.0 is running
    Affected if Version is neither 5.0 nor 6.0 - not affected
  3. Determine the build number
    Check the build version of the installed HP Data Protector Express - typically visible in the product's version info, about screen, or installation logs
    Affected if Build number cannot be determined - assume potentially affected
  4. Compare build to vulnerable ranges
    For version 5.0: check if build is below 59287. For version 6.0: check if build is below 11974
    Affected if Version 5.0 build < 59287 OR Version 6.0 build < 11974 - affected
  5. Assess network exposure
    Determine if DPX services are accessible from untrusted networks - check firewall rules and exposed ports used by the product
    Affected if Service is network-accessible without authentication - exploit potential increases significantly

User is affected if HP Data Protector Express version 5.0 with build < 59287 or version 6.0 with build < 11974 is installed, especially if network-accessible.

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

Update HP Data Protector Express to build 59287 or later for version 5.0.00, and build 11974 or later for version 6.0.00. If patching is not immediately feasible, restrict network access to DPX services and monitor for indicators of compromise.

Recommended fix High confidence

HP Data Protector Express 5.0 build 59287+ or 6.0 build 11974+

  1. 1. Identify the currently installed HP Data Protector Express build version.
  2. 2. For HP Data Protector Express 5.0.x: Upgrade to build 59287 or later.
  3. 3. For HP Data Protector Express 6.0.x: Upgrade to build 11974 or later.
  4. 4. Verify the upgrade was successful by confirming the new build number.
  5. 5. Test critical backup/restore operations to ensure functionality is intact.
  6. 6. Review any post-upgrade documentation for configuration changes.

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

Fix this in Data Protector Express Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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