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

> Attackers can execute arbitrary system commands as root by injecting special characters into certificate fields on the administrator page.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wjqc-hf5j-wc82

## What is CVE-2019-11355?

CVE-2019-11355 is a high-severity command injection vulnerability in n/a, published on 12 Mar 2020. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in Poly (formerly Polycom) HDX 3.1.13. A feature exists that allows the creation of a server / client certificate, or the upload of the user certificate, on the administrator's page. The value received from the user is the factor value of a shell script on the equipment. By entering a special character (such as a single quote) in a CN or other CSR field, one can insert a command into a factor value. A system command can be executed as root.

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

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

It affects 1 product.


Products: Polycom Hdx System Software.

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

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

## Is CVE-2019-11355 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-6611](https://insights.sbomify.com/CVE-2012-6611/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2012-4970](https://insights.sbomify.com/CVE-2012-4970/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-11355 is a high-severity command injection vulnerability in n/a, published on 12 Mar 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-11355 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-11355/ (Markdown: https://insights.sbomify.com/CVE-2019-11355/index.md)
```

## Sources

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

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