# CVE-2018-20162: Command injection in n/a

> Users with super CLI access can bypass restricted shells to execute arbitrary commands as root on Digi TransPort LR54 devices.

- **Severity:** Critical 9.9 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/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:** 17 Mar 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qqq3-6v7x-728w

## What is CVE-2018-20162?

CVE-2018-20162 is a critical command injection vulnerability in n/a, published on 17 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Digi TransPort LR54 4.4.0.26 and possible earlier devices have Improper Input Validation that allows users with 'super' CLI access privileges to bypass a restricted shell and execute arbitrary commands as root.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Digi Transport Lr54 Firmware.

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

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

## Is CVE-2018-20162 being exploited?

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

Public exploit code:

- https://github.com/stigtsp/CVE-2018-20162-digi-lr54-restricted-shell-escape (github_poc): https://github.com/stigtsp/CVE-2018-20162-digi-lr54-restricted-shell-escape

## Fix prompt for AI coding agents

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

What it is: CVE-2018-20162 is a critical command injection vulnerability in n/a, published on 17 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-20162 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-2018-20162/ (Markdown: https://insights.sbomify.com/CVE-2018-20162/index.md)
```

## Sources

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

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