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

> Remote attackers can execute arbitrary OS commands on DBLTek devices by exploiting a command injection vulnerability in the password change functionality.

- **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:** 24 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qjgc-mf9m-9xq4

## What is CVE-2017-16934?

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

### Official description

The web server on DBL DBLTek devices allows remote attackers to execute arbitrary OS commands by obtaining the admin password via a frame.html?content=/dev/mtdblock/5 request, and then using this password for the HTTP Basic Authentication needed for a change_password.csp request, which supports a "<%%25call system.exec:" string in the passwd parameter.

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

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

It affects 1 product.


Products: Dbltek Web Server.

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

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

## Is CVE-2017-16934 being exploited?

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

Public exploit code:

- DblTek - Multiple Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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