Easy Printer Care SoftwareApplication · Hp

CVE-2011-4787

HIGH · 9.3 CVSS v2.0 Published 2012-01-12
Fix available
A fix is available. Upgrade to after 2.5 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
A certain ActiveX control in HPTicketMgr.dll in HP Easy Printer Care Software 2.5 and earlier allows remote attackers to download an arbitrary program onto a client machine, and execute this program, via unspecified vectors, a different vulnerability than CVE-2011-2404 and CVE-2011-4786.

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

An ActiveX control in HPTicketMgr.dll within HP Easy Printer Care Software 2.5 and earlier allows remote attackers to download and execute arbitrary programs on the client machine via unspecified vectors, achieving remote code execution with high severity (CVSS 9.3).

MitigationUpgrade HP Easy Printer Care Software to a version beyond 2.5 that includes the patched ActiveX control, or disable the vulnerable HPTicketMgr.dll ActiveX control in Internet Explorer as a workaround.

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
Easy Printer Care SoftwareApplication
Affected:<= 2.5

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

AV:N/AC:M/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. Check if HP Easy Printer Care Software is installed
    Open Programs and Features (appwiz.cpl) or check the installation directory (typically C:\Program Files\HP or C:\Program Files (x86)\HP\Easy Printer Care) for the software folder
    Affected if HP Easy Printer Care Software is present on the system
  2. Determine the installed version of HP Easy Printer Care
    Locate the software in Program Files, right-click the executable or check version information in file properties, or look in the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for HP Easy Printer Care entry
    Affected if The version is 2.5 or earlier, or if no version information is displayed and the software predates 2011
  3. Verify presence of the vulnerable HPTicketMgr.dll ActiveX control
    Search for HPTicketMgr.dll in the HP Easy Printer Care installation directory (commonly C:\Program Files\HP\Easy Printer Care\ or subfolders)
    Affected if The file HPTicketMgr.dll exists in the installation directory
  4. Check if the ActiveX control is registered in Internet Explorer
    Open Windows Registry and look for the CLSID of HPTicketMgr.dll under HKCR\CLSID\ or HKLM\SOFTWARE\Classes\, or view registered ActiveX controls in Internet Explorer via Manage Add-ons
    Affected if The ActiveX control CLSID for HPTicketMgr.dll is registered and enabled in Internet Explorer

If HP Easy Printer Care Software version 2.5 or earlier is installed with the HPTicketMgr.dll ActiveX control present and registered, the system is vulnerable to remote code execution via this CVE.

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
Upgrade available Upgrade to a release after 2.5
Interim mitigation

Upgrade HP Easy Printer Care Software to a version beyond 2.5 that includes the patched ActiveX control, or disable the vulnerable HPTicketMgr.dll ActiveX control in Internet Explorer as a workaround.

Fix this in Easy Printer Care Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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