CVE-2019-14717
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 · uneditedVerifone Verix OS on VerixV Pinpad Payment Terminals with QT000530 have a Buffer Overflow via the Run system call.
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 · moderate confidenceA buffer overflow vulnerability exists in Verifone Verix OS on VerixV Pinpad Payment Terminals (QT000530) where the Run system call fails to properly validate input buffer length before copying data. This memory corruption issue could allow an attacker to overwrite adjacent memory, potentially leading to arbitrary code execution or denial of service on the payment terminal.
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= qt000530CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 terminal model and firmware versionAccess the terminal's system information or diagnostics menu, typically via the merchant menu or by checking the startup banner. Look for the model identifier (VerixV Pinpad) and firmware version string.Affected if The terminal model is VerixV Pinpad with firmware version QT000530
-
Verify the Run system call is accessibleCheck if the terminal exposes an interface or API that allows invocation of the Run system call. This may be through an application menu, remote management interface, or diagnostic port.Affected if The Run system call functionality is enabled or accessible on the terminal
-
Check for unvalidated input handling in custom applicationsReview any custom applications or scripts running on the terminal that invoke the Run system call. Look for code that passes user-controlled data to the Run function without length validation.Affected if Applications pass unsanitized input buffers to the Run system call
-
Review terminal audit logs for Run system call usageExamine terminal event logs or audit trails for invocations of the Run system call, especially those with unusual or unexpected input patterns that could indicate exploitation attempts.Affected if Logs show abnormal Run system call behavior or potential exploitation indicators
A defender is affected if they operate VerixV Pinpad terminals with firmware version QT000530 and the Run system call functionality is present and accessible without proper input validation safeguards.
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.
From vendor dataApply the vendor-provided firmware patch or security update for VerixV Pinpad terminals. If no patch is available, isolate affected terminals on restricted network segments and implement compensating controls such as transaction monitoring and enhanced logging.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14717 — 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-2019-14717 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