Data Protector For Personal ComputersApplication · Hp

CVE-2011-3162

HIGH · 10.0 CVSS v2.0 Published 2011-10-19
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 Notebook Extension 6.20 and Data Protector for Personal Computers 7.0 allows remote attackers to execute arbitrary code via unknown vectors, aka ZDI-CAN-1296.

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 Notebook Extension 6.20 and Data Protector for Personal Computers 7.0 contain an unspecified vulnerability allowing remote attackers to execute arbitrary code without authentication. The CVSS 10 score indicates the vulnerability is network-exploitable with no user interaction required and complete impact on confidentiality, integrity, and availability.

MitigationApply HP security patches for Data Protector immediately; if no patch available, network-segment the affected systems and restrict access to Data Protector ports/services until a fix is released.

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 For Personal ComputersApplication
Affected:= 7.0
Data Protector Notebook ExtensionPlugin / extension
Affected:= 6.20

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 installation
    Check system for installed HP Data Protector software. On Windows, review installed programs in Control Panel > Programs and Features. On Linux, run 'dpkg -l | grep -i "data protector"' or 'rpm -qa | grep -i "data protector"'.
    Affected if HP Data Protector for Personal Computers version 7.0 or HP Data Protector Notebook Extension version 6.20 is listed as installed
  2. Verify exact version number
    Access the software version information. In Windows, right-click the application in Programs and Features and select Properties > Version. On Linux, check '/opt/DP' directory or run the product's version command if available.
    Affected if Installed version exactly matches 7.0 (Personal Computers) or 6.20 (Notebook Extension)
  3. Confirm Notebook Extension component
    Inspect whether the Notebook Extension component is present. Look for 'Data Protector Notebook Extension' in installed programs, or check program directories for notebook-related modules.
    Affected if HP Data Protector Notebook Extension version 6.20 is present on the system
  4. Check if Data Protector service is running
    Review running services. On Windows, open Services console and look for 'HP Data Protector' services. On Linux, run 'ps aux | grep -i dp' or check '/etc/init.d/' for Data Protector scripts.
    Affected if Data Protector service is actively running and listening on network ports

Your environment is affected if HP Data Protector for Personal Computers 7.0 or HP Data Protector Notebook Extension 6.20 is installed AND the service is running and 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply HP security patches for Data Protector immediately; if no patch available, network-segment the affected systems and restrict access to Data Protector ports/services until a fix is released.

Fix this in Data Protector For Personal Computers Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2011-3162 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