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

> Attackers can execute arbitrary code on Verifone Verix terminals by exploiting a buffer overflow in the Multi-app Conductor application via a long configuration key.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-46vp-348f-8cxx

## What is CVE-2019-10060?

CVE-2019-10060 is a high-severity memory corruption vulnerability in n/a, published on 25 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Verix Multi-app Conductor application 2.7 for Verifone Verix suffers from a buffer overflow vulnerability that allows attackers to execute arbitrary code via a long configuration key value. An attacker must be able to download files to the device in order to exploit this vulnerability.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Verifone Verix Multi-App Conductor.

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

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

## Is CVE-2019-10060 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10060 is a high-severity memory corruption vulnerability in n/a, published on 25 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10060 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-10060/ (Markdown: https://insights.sbomify.com/CVE-2019-10060/index.md)
```

## Sources

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

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