# CVE-2019-9972: Command injection in n/a

> An authenticated attacker can execute arbitrary commands with phonesystem privileges in 3CX Phone System via input mishandling.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jun 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9wgp-3xm8-wjwj

## What is CVE-2019-9972?

CVE-2019-9972 is a high-severity command injection vulnerability in Debian Debian Linux, published on 7 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PhoneSystem Terminal in 3CX Phone System (Debian based installation) 16.0.0.1570 allows an authenticated attacker to run arbitrary commands with the phonesystem user privileges because of "<space><space> followed by <shift><enter>" mishandling.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 2 products.


Products: 3cx Phone System Firmware, Debian Debian Linux.

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

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

## Is CVE-2019-9972 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2019-9971](https://insights.sbomify.com/CVE-2019-9971/): Privilege escalation in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-9972 is a high-severity command injection vulnerability in Debian Debian Linux, published on 7 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-9972 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-9972/ (Markdown: https://insights.sbomify.com/CVE-2019-9972/index.md)
```

## Sources

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

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