dbcve.org
Ole Point Of Sale DriverApplication · Hp

CVE-2014-7890

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

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

OPOS (OLE Point of Sale) drivers before version 1.13.003 contain a vulnerability in the OPOSToneIndicator.ocx ActiveX control used by HP Point of Sale Windows PCs with POS keyboards and POS keyboards with MSR (Magnetic Stripe Reader). Remote attackers can exploit this to execute arbitrary code, likely through a buffer overflow or similar memory corruption issue in the ActiveX control.

MitigationUpgrade OPOS drivers to version 1.13.003 or later. If immediate patching is not feasible, disable or restrict access to the vulnerable ActiveX control and network-level access to POS systems.

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 OPOS driver installation directory
    Search the system for OPOSToneIndicator.ocx file using file search or check typical installation paths for HP POS software (e.g., C:\Program Files\HP\OPOS or C:\Program Files\Common Files\OPOS)
    Affected if The OPOSToneIndicator.ocx file exists on the system - this indicates the vulnerable ActiveX component is installed
  2. Check HP Ole Point of Sale Driver version
    Open Windows Control Panel > Programs and Features, locate 'HP Ole Point of Sale Driver' or similar entry, and view the installed version; alternatively, right-click the driver file and select Properties > Details to view version information
    Affected if The installed version is 1.13.001 or earlier (any version listed as 'less than or equal to 1.13.001' per the affected product range)
  3. Verify ActiveX control registration
    Open Command Prompt and run 'regsvr32 /u OPOSToneIndicator.ocx' from the installation directory to check if the control is registered; check Windows Registry under HKLM\SOFTWARE\Classes\OPOSToneIndicator for ActiveX control registration entries
    Affected if The ActiveX control is registered and enabled on the system (control appears in registry without error)
  4. Confirm HP POS keyboard or MSR device context
    Verify the system is a HP Point of Sale Windows PC with POS keyboards or POS keyboards with Magnetic Stripe Reader (MSR) - check device manager for HP POS keyboard or MSR hardware entries
    Affected if The system is an HP POS device using POS keyboards or POS keyboards with MSR, as these are the specific products mentioned as affected

If the system has HP Ole Point of Sale Driver version 1.13.001 or earlier, contains the OPOSToneIndicator.ocx ActiveX control, and is an HP POS device with POS keyboards or MSR, then the environment is vulnerable to CVE-2014-7890.

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. If immediate patching is not feasible, disable or restrict access to the vulnerable ActiveX control and network-level access to POS systems.

Recommended fix High confidence

OPOS drivers version 1.13.003 or later

  1. Verify the current version of OPOS (OLE Point of Sale) drivers installed on the HP Point of Sale system by checking the OPOSToneIndicator.ocx file version or through Windows Programs and Features
  2. Navigate to the HP support website (h20564.www2.hp.com) or the official HP software download repository
  3. Search for 'OPOS drivers' or 'OLE Point of Sale' and locate version 1.13.003 or later
  4. Download the updated OPOS driver package version 1.13.003 or newer
  5. Close any POS applications that may be using the OPOSToneIndicator.ocx component
  6. Run the HP OPOS driver installer to update the software
  7. Restart the system after installation completes
  8. Verify the updated version is 1.13.003 or later by checking the OPOSToneIndicator.ocx properties

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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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