# CVE-2017-14135: Command injection in n/a

> Remote attackers can execute arbitrary OS commands via shell metacharacters in the webadmin plugin of Opendreambox 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:** 4 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9hmm-f56w-7jj9

## What is CVE-2017-14135?

CVE-2017-14135 is a critical command injection vulnerability in n/a, published on 4 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

enigma2-plugins/blob/master/webadmin/src/WebChilds/Script.py in the webadmin plugin for opendreambox 2.0.0 allows remote attackers to execute arbitrary OS commands via shell metacharacters in the command parameter to the /script URI.

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

## Which versions are affected by CVE-2017-14135?

It affects 1 product.


Products: Dreambox Opendreambox.

## How do I fix CVE-2017-14135?

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

## Is CVE-2017-14135 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-14135 exists.

Public exploit code:

- OpenDreambox 2.0.0 - Remote Code Execution (nuclei): http/cves/2017/CVE-2017-14135.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14135 and fix it if it is affected.

What it is: CVE-2017-14135 is a critical command injection vulnerability in n/a, published on 4 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-14135 exists.

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-2017-14135/ (Markdown: https://insights.sbomify.com/CVE-2017-14135/index.md)
```

## Sources

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

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