# CVE-2013-2571: Command injection in n/a

> Remote attackers can execute arbitrary commands on Xpient POS systems via crafted requests, potentially compromising the device.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3gfr-cm88-25f2

## What is CVE-2013-2571?

CVE-2013-2571 is a critical command injection vulnerability in n/a, published on 28 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Iris 3.8 before build 1548, as used in Xpient point of sale (POS) systems, allows remote attackers to execute arbitrary commands via a crafted request to TCP port 7510, as demonstrated by opening the cash drawer.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2013-2571?

It affects 1 product.


Products: Hcomm Xpient Iris.

## How do I fix CVE-2013-2571?

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

## Is CVE-2013-2571 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-2571 exists.

Public exploit code:

- Xpient - Cash Drawer Operation (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2571 and fix it if it is affected.

What it is: CVE-2013-2571 is a critical command injection vulnerability in n/a, published on 28 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-2571 exists.

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-2013-2571/ (Markdown: https://insights.sbomify.com/CVE-2013-2571/index.md)
```

## Sources

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

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