CVE-2019-14715
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 Pinpad Payment Terminals allow undocumented physical access to the system via an SBI bootloader memory write operation.
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 confidenceVerifone Pinpad Payment Terminals contain an undocumented SBI bootloader memory write operation that allows unauthorized physical access to modify firmware, potentially enabling security bypass or malware injection.
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 dataall versionsall versionsall versionsall versionsCVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/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 the terminal modelLocate the device model label on the physical terminal or query the device's system information/status screen. Common locations include the back of the device, the base, or the system settings menu under 'Device Info' or 'About'.Affected if The model is one of: P400, P200, Vx 820, or Vx 805.
-
Check physical location securityVerify the terminal is placed in a physically secure area with restricted access. Document whether the terminal is in a publicly accessible location, behind a counter, or in a locked enclosure.Affected if The terminal is in an area accessible to unauthorized individuals.
-
Inspect tamper-evident sealsExamine all seals on the terminal chassis, particularly around the battery compartment, cable connections, and any screws. Check if seals are intact, unbroken, and match the expected vendor seal pattern.Affected if Tamper seals are missing, damaged, or show signs of tampering.
-
Verify bootloader interface accessibilityAttempt to access the SBI bootloader interface by following the undocumented procedure (typically involves specific key combinations during boot or serial/JTAG access). Document whether the bootloader accepts memory write commands without authentication.Affected if The bootloader interface is accessible and accepts unauthenticated memory write operations.
If the terminal model is P400, P200, Vx 820, or Vx 805 and the device has unrestricted physical access or compromised tamper seals, the environment is affected by this vulnerability.
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 dataOrganizations should restrict physical access to terminals, implement tamper-evident seals, and apply vendor-provided firmware updates that disable or secure the undocumented bootloader interface.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.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 $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14715 — 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-14715 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