dbcve.org
Ole Point Of Sale DriverApplication · Hp

CVE-2014-7892

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 OPOSMSR.ocx for Mini MSR magnetic stripe readers, Retail Integrated Dual-Head MSR magnetic stripe readers, Integrated Single Head MSR w/o SRED magnetic stripe readers, Integrated Single Head w/o MSR SRED magnetic stripe readers, RP7 Single Head MSR w/o SRED magnetic stripe readers, POS keyboards, and POS keyboards with MSR, aka ZDI-CAN-2508.

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

Remote code execution vulnerability in the OPOSMSR.ocx ActiveX control within HP Point of Sale OPOS drivers before version 1.13.003. The vulnerability affects multiple MSR magnetic stripe reader models and POS keyboards, allowing remote attackers to execute arbitrary code via the vulnerable ActiveX component.

MitigationUpdate OPOS drivers to version 1.13.003 or later on all affected HP Point of Sale Windows systems. Consider network segmentation to limit exposure of POS terminals until patches are applied.

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. Verify HP OPOS driver is installed
    Open Windows Control Panel > Programs and Features, or run 'wmic product get name,version' and look for 'HP Ole Point Of Sale Driver' or HP OPOS driver entries
    Affected if The HP Ole Point of Sale Driver is present on the system
  2. Locate the OPOSMSR.ocx ActiveX component
    Search for OPOSMSR.ocx in the Windows system directories, typically found in C:\Windows\System32\ or C:\Windows\SysWOW64\, or check the HP OPOS installation directory
    Affected if The OPOSMSR.ocx file exists on the system
  3. Retrieve the driver or ActiveX component version
    Right-click the OPOSMSR.ocx file, select Properties, then view the Version tab. Alternatively, check the version field in Programs and Features for the HP Ole Point of Sale Driver entry
    Affected if The version displayed is 1.13.001 or earlier, or the version cannot be determined but the driver appears to be an older release
  4. Confirm the vulnerable configuration
    Verify the HP Point of Sale system uses MSR magnetic stripe reader functionality - check if the OPOSMSR service is running or if POS applications reference the MSR reader
    Affected if The MSR ActiveX control is actively used or registered on the POS terminal

A system is affected if HP Ole Point of Sale Driver version 1.13.001 or earlier is installed, and the OPOSMSR.ocx ActiveX component is present on a Windows POS terminal.

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 Windows systems. Consider network segmentation to limit exposure of POS terminals until patches are applied.

Recommended fix High confidence

OPOS drivers version 1.13.003

  1. Identify the current OPOS driver version installed on the HP Point of Sale system by checking the file properties of OPOSMSR.ocx or using the Add/Remove Programs list
  2. Navigate to HP's official support website and locate the OPOS driver version 1.13.003 or later for your specific HP Point of Sale model
  3. Download the updated OPOS driver package from HP support
  4. Backup the current system configuration and any critical POS data before proceeding with the update
  5. Run the HP OPOS driver installer with administrator privileges
  6. Follow the on-screen installation prompts to complete the driver update
  7. Restart the HP Point of Sale system as directed by the installer
  8. Verify the OPOS driver version is now 1.13.003 or higher by checking the file properties of OPOSMSR.ocx

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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