dbcve.org
Ole Point Of Sale DriverApplication · Hp

CVE-2014-7889

HIGH · 10.0 CVSS v2.0 Published 2015-03-09
Fix available
A fix is available. Upgrade to after 1.13.001 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
The OLE Point of Sale (OPOS) drivers before 1.13.003 on HP Point of Sale Windows PCs allow remote attackers to execute arbitrary code via vectors involving OPOSLineDisplay.ocx for Retail RP7 VFD Customer Display monitors, Retail Integrated 2x20 Display monitors, Retail Integrated 2x20 Complex monitors, POS Pole Display monitors, Graphical POS Pole Display monitors, and LCD Pole Display monitors, aka ZDI-CAN-2511.

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

A remote code execution vulnerability exists in OPOS (OLE for Point of Sale) drivers before version 1.13.003 on HP Point of Sale Windows systems. The vulnerability resides in the OPOSLineDisplay.ocx ActiveX control used by multiple retail display monitors, allowing attackers to execute arbitrary code remotely.

MitigationUpdate OPOS drivers to version 1.13.003 or later on all affected HP POS terminals. If immediate patching is not possible, network-segment POS systems and disable the OPOSLineDisplay.ocx ActiveX control.

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
Ole Point Of Sale DriverApplication
Affected:<= 1.13.001

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. Locate OPOSLineDisplay.ocx on the system
    Search for the file OPOSLineDisplay.ocx in typical Windows system directories (C:\Windows\System32, C:\Windows\SysWOW64) or use: Get-ChildItem -Path C:\ -Filter OPOSLineDisplay.ocx -Recurse -ErrorAction SilentlyContinue
    Affected if The file exists on the system
  2. Check the version of the OPOS driver or ActiveX control
    Right-click the OPOSLineDisplay.ocx file, select Properties, then view the Details tab to find the File Version. Alternatively, check the installed HP Ole Point of Sale Driver version via Control Panel > Programs and Features
    Affected if The version is 1.13.001 or lower (the vulnerable range)
  3. Verify the ActiveX control is registered
    Open Command Prompt and run: regsvr32 OPOSLineDisplay.ocx (to check registration status) or check the registry key HKEY_CLASSES_ROOT\OPOSLineDisplay.ActiveXControl for presence
    Affected if The control is registered and present on a HP POS system
  4. Confirm the product is HP Point of Sale
    Check system information or review installed programs for HP Ole Point Of Sale Driver or HP POS-related software. Check Program Files for HP Point of Sale directories
    Affected if HP Ole Point of Sale Driver is installed and the version is 1.13.001 or below

The system is affected if OPOSLineDisplay.ocx is present AND the HP Ole Point of Sale Driver version is 1.13.001 or lower.

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.13.001
Interim mitigation

Update OPOS drivers to version 1.13.003 or later on all affected HP POS terminals. If immediate patching is not possible, network-segment POS systems and disable the OPOSLineDisplay.ocx ActiveX control.

Recommended fix High confidence

1.13.003

  1. Download OPOS drivers version 1.13.003 or later from HP support site
  2. Install the updated OPOS drivers on affected HP Point of Sale Windows PCs
  3. Verify the OPOSLineDisplay.ocx component is updated to the patched version
  4. Restart any POS applications that utilize the OPOS drivers

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

Fix this in Ole Point Of Sale Driver Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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