CVE-2014-7893
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 · uneditedThe 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 OPOSCheckScanner.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-2507.
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 confidenceHP OPOS (OLE Point of Sale) drivers before version 1.13.003 contain a remote code execution vulnerability in the OPOSCheckScanner.ocx ActiveX control. The vulnerability affects multiple HP Point of Sale thermal receipt printer models (PUSB, SerialUSB, Hybrid POS with MICR, and Value Receipt printers). Attackers can exploit this to execute arbitrary code via the vulnerable ActiveX component.
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<= 1.13.001CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed HP OPOS driver versionOpen Windows Control Panel > Programs and Features, or run 'wmic product get name,version' to list installed HP OPOS-related software. Look for 'HP Ole Point Of Sale Driver' or similar HP POS driver packages and note the version number.Affected if The installed version is 1.13.001 or earlier, or if the version cannot be determined but the driver is present.
-
Locate OPOSCheckScanner.ocx ActiveX controlSearch for the file OPOSCheckScanner.ocx in typical Windows system directories such as C:\Windows\System32\, C:\Windows\SysWOW64\, or the HP driver installation directory (commonly under C:\Program Files\HP\ or C:\Program Files (x86)\HP\).Affected if The file OPOSCheckScanner.ocx exists on the system.
-
Verify ActiveX control registrationOpen Command Prompt and run 'reg query "HKLM\SOFTWARE\Classes\OPOSCheckScanner.CheckScanner"' or 'reg query "HKCU\SOFTWARE\Classes\OPOSCheckScanner.CheckScanner"' to check if the ActiveX control is registered as a COM object.Affected if The ActiveX control is registered in the Windows registry.
-
Check for vulnerable HP POS printer modelsReview installed printer drivers or physically identify connected HP Point of Sale thermal receipt printers. Look for models labeled as PUSB, SerialUSB, Hybrid POS with MICR, or Value Receipt printers.Affected if Any of these specific HP POS printer models are installed or connected, and the OPOS driver version is 1.13.001 or earlier.
A system is affected if HP Ole Point Of Sale Driver version 1.13.001 or earlier is installed, the OPOSCheckScanner.ocx ActiveX control is present, and vulnerable HP POS thermal receipt printer models (PUSB, SerialUSB, Hybrid POS with MICR, or Value Receipt) are in use.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate HP OPOS drivers to version 1.13.003 or later. If immediate patching is not feasible, implement network segmentation to restrict unauthorized access to POS systems and disable or remove the vulnerable OPOSCheckScanner.ocx ActiveX control.
OPOS driver version 1.13.003 or later
- Identify the current version of OPOS driver installed on the HP Point of Sale system by checking the driver file properties or using Windows Device Manager
- Navigate to the official HP support website (h20564.www2.hp.com) or HP's software download page
- Search for OPOS (OLE Point of Sale) driver version 1.13.003 or later for HP Point of Sale
- Download the updated OPOS driver package (version 1.13.003 or newer)
- Close any applications that use the POS peripherals (receipt printers, scanners, etc.)
- Run the installer and follow the on-screen prompts to upgrade the OPOS driver
- Restart the system if prompted by the installer
- Verify the installed version is 1.13.003 or later through Device Manager or the OPOS service control panel
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-7893 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-7893 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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