# CVE-2018-5553: Crestron DGE-100 Console Command Injection (FIXED)

> Attackers can inject commands via the console service to gain root access on Crestron AV devices.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 10 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-chvw-4j9v-9x4r

## What is CVE-2018-5553?

CVE-2018-5553 is a critical command injection vulnerability in Crestron DGE-100, published on 10 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Crestron Console service running on DGE-100, DM-DGE-200-C, and TS-1542-C devices with default configuration and running firmware versions 1.3384.00049.001 and lower are vulnerable to command injection that can be used to gain root-level access.

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

## Which versions are affected by CVE-2018-5553?

It affects 3 products.


Products: Crestron Dge-100 Firmware, Crestron Dm-Dge-200-C Firmware, Crestron Ts-1542-C Firmware.

## How do I fix CVE-2018-5553?

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

## Is CVE-2018-5553 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-5553 and fix it if it is affected.

What it is: CVE-2018-5553 is a critical command injection vulnerability in Crestron DGE-100, published on 10 Jul 2018. 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-2018-5553 in the wild and no public exploit code.

Affected product: Crestron DGE-100. 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-2018-5553/ (Markdown: https://insights.sbomify.com/CVE-2018-5553/index.md)
```

## Sources

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

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