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

> An authenticated remote attacker can execute arbitrary OS commands on the Atcom A10W VoIP phone via shell metacharacters in the web interface.

- **Severity:** Critical 9.0 (`CVSS:3.0/AC:L/AV:A/A:H/C:H/I:H/PR:L/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hrcx-g752-fgp2

## What is CVE-2019-12328?

CVE-2019-12328 is a critical command injection vulnerability in n/a, published on 22 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A command injection (missing input validation) issue in the remote phonebook configuration URI in the web interface of the Atcom A10W VoIP phone with firmware 2.6.1a2421 allows an authenticated remote attacker in the same network to trigger OS commands via shell metacharacters in a POST request.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Atcom A10w Firmware.

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

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

## Is CVE-2019-12328 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-12328 is a critical command injection vulnerability in n/a, published on 22 Jul 2019. 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-12328 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-12328/ (Markdown: https://insights.sbomify.com/CVE-2019-12328/index.md)
```

## Sources

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

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