dbcve.org
Ole Point Of Sale DriverApplication · Hp

CVE-2014-7891

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 OPOSPOSKeyboard.ocx for POS keyboards and POS keyboards with MSR, aka ZDI-CAN-2509.

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

This is a remote code execution vulnerability in the OPOS (OLE Point of Sale) driver component OPOSPOSKeyboard.ocx affecting HP Point of Sale Windows PCs. Attackers can exploit this vulnerability remotely to execute arbitrary code without authentication, achieving complete system compromise given the CVSS 10 score.

MitigationUpgrade OPOS drivers to version 1.13.003 or later to remediate this vulnerability. Apply the update across all affected HP POS systems following vendor deployment guidance.

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 OPOSPOSKeyboard.ocx on the system
    Search for the file OPOSPOSKeyboard.ocx in typical locations such as C:\Windows\System32\, C:\Windows\SysWOW64\, or the HP POS software installation directory. Use the command: dir /s /b C:\OPOSPOSKeyboard.ocx 2>nul
    Affected if The file exists on the system
  2. Check the file version of OPOSPOSKeyboard.ocx
    Right-click the ocx file, select Properties, then navigate to the Details tab to view the File Version. Alternatively, use PowerShell: (Get-Item 'C:\Path\To\OPOSPOSKeyboard.ocx').VersionInfo.FileVersion
    Affected if The reported version is 1.13.001 or earlier
  3. Identify the HP OPOS Driver version via registry
    Check the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup or look for HP OPOS entries under HKEY_CLASSES_ROOT\OPOSPOSKeyboard. Use regedit or PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup' | Select-Object *
    Affected if The installed OPOS driver version is 1.13.001 or earlier, or the version cannot be determined but the ocx file is present
  4. Confirm this is an HP Point of Sale system
    Review system information or check for HP POS software packages installed. Use Programs and Features (appwiz.cpl) or PowerShell: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*HP*POS*'}
    Affected if HP Point of Sale software is installed and the driver version meets the affected criteria

A user is affected if OPOSPOSKeyboard.ocx is present and its version is 1.13.001 or earlier on an HP Point of Sale Windows system.

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

Upgrade OPOS drivers to version 1.13.003 or later to remediate this vulnerability. Apply the update across all affected HP POS systems following vendor deployment guidance.

Recommended fix High confidence

1.13.003

  1. Identify the current version of OPOS (Ole Point Of Sale) driver installed on the HP Point of Sale system
  2. Navigate to the HP support website (h20564.www2.hp.com) or official HP support channels
  3. Search for OPOS driver version 1.13.003 or later
  4. Download the updated OPOS driver package
  5. Apply the update to the HP Point of Sale system following HP's installation instructions
  6. Verify the updated driver version is 1.13.003 or later after installation

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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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