dbcve.org
Ole Point Of Sale DriverApplication · Hp

CVE-2014-7894

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 OPOSPOSPrinter.ocx for PUSB Thermal Receipt printers, SerialUSB Thermal Receipt printers, Hybrid POS printers with MICR, Value PUSB Receipt printers, and Value Serial/USB Receipt printers, aka ZDI-CAN-2506.

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

HP Point of Sale systems running OPOS (OLE Point of Sale) drivers before version 1.13.003 contain a critical vulnerability in the OPOSPOSPrinter.ocx ActiveX control. Remote attackers can exploit this to execute arbitrary code via malformed requests to PUSB, SerialUSB, Hybrid POS with MICR, and Value Receipt printers. The CVSS 10 score indicates network-exploitable, low-complexity attacks with complete system compromise possible.

MitigationUpdate OPOS drivers to version 1.13.003 or later on all affected HP Point of Sale systems. If patches are unavailable, isolate POS systems on dedicated network segments and disable unnecessary printer communication ports.

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. Identify HP POS system and OPOS installation
    Check system information for HP Point of Sale hardware and verify OPOS (OLE Point of Sale) drivers are installed. Look for OPOSPOSPrinter.ocx in system directories (typically C:\Windows\System32\ or C:\Windows\SysWOW64\) or check Add/Remove Programs for HP OPOS drivers.
    Affected if System is an HP Point of Sale and OPOSPOSPrinter.ocx is present but version is unknown or <= 1.13.001
  2. Verify OPOS driver version
    Right-click on OPOSPOSPrinter.ocx file, select Properties, then inspect the File Version field. Alternatively, check the installed HP OPOS driver version through Windows Registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or check the driver package version if available.
    Affected if Driver version is 1.13.001 or earlier, or version cannot be determined and the file exists
  3. Confirm affected printer types are in use
    Review POS configuration to determine if PUSB, SerialUSB, Hybrid POS with MICR, or Value Receipt printers are enabled or configured. Check POS software printer settings or device manager for these printer types.
    Affected if Any of the affected printer types (PUSB, SerialUSB, Hybrid POS with MICR, or Value Receipt) are configured or active on the system
  4. Check ActiveX control accessibility
    Verify that OPOSPOSPrinter.ocx ActiveX control is registered and accessible. Check Windows Registry under HKEY_CLASSES_ROOT\OPOSPOSPrinter for the component registration.
    Affected if OPOSPOSPrinter.ocx is registered and accessible on the system, indicating the attack surface is present

A user is affected if their HP POS system runs OPOS drivers version 1.13.001 or earlier with OPOSPOSPrinter.ocx present and any of the affected printer types configured.

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 Point of Sale systems. If patches are unavailable, isolate POS systems on dedicated network segments and disable unnecessary printer communication ports.

Recommended fix High confidence

OPOS drivers version 1.13.003

  1. Identify the current version of HP OLE Point of Sale (OPOS) drivers installed on the system
  2. Download OPOS driver version 1.13.003 or later from HP's official support website
  3. Ensure all Point of Sale applications are closed before upgrading
  4. Run the OPOS driver installer with administrative privileges
  5. Follow the on-screen installation prompts to complete the upgrade
  6. Restart the system if prompted by the installer
  7. Verify the installed version is 1.13.003 or higher via the OPOS control panel or system information

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
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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