# CVE-2019-14715: Memory corruption in n/a

> Attackers with physical access can exploit an SBI bootloader memory write to gain undocumented system access on Verifone Pinpad terminals.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Oct 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-279x-vjpx-pq4v

## What is CVE-2019-14715?

CVE-2019-14715 is a medium-severity memory corruption vulnerability in n/a, published on 23 Oct 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Verifone Pinpad Payment Terminals allow undocumented physical access to the system via an SBI bootloader memory write operation.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2019-14715?

It affects 4 products.


Products: Verifone P200 Firmware, Verifone P400 Firmware, Verifone Vx 805 Firmware, Verifone Vx 820 Firmware.

## How do I fix CVE-2019-14715?

No fix has been published for CVE-2019-14715 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-14715 being exploited?

There is no known exploitation of CVE-2019-14715 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-14715 and fix it if it is affected.

What it is: CVE-2019-14715 is a medium-severity memory corruption vulnerability in n/a, published on 23 Oct 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-14715 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-14715/ (Markdown: https://insights.sbomify.com/CVE-2019-14715/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-14715
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-14715
- OSV: https://osv.dev/vulnerability/CVE-2019-14715

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-14715/
Summaries are generated and may contain mistakes; the official description above is the record.