# CVE-2016-6534: Command injection in Opmantek NMIS before 8.5.12G

> Attackers can execute arbitrary commands via network tools in Opmantek NMIS, potentially compromising the system.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/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:** 10 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-933m-qxvc-7xc2

## What is CVE-2016-6534?

CVE-2016-6534 is a high-severity command injection vulnerability in Opmantek NMIS before 8.5.12G, published on 10 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Opmantek NMIS before 4.3.7c has command injection via man, finger, ping, trace, and nslookup in the tools.pl CGI script. Versions before 8.5.12G might be affected in non-default configurations.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2016-6534?

It affects 1 product.


Products: Opmantek Network Management Information System.

## How do I fix CVE-2016-6534?

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

## Is CVE-2016-6534 being exploited?

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

## Other vulnerabilities in Opmantek NMIS before 8.5.12G

- [CVE-2016-5642](https://insights.sbomify.com/CVE-2016-5642/): Cross-site scripting in Opmantek NMIS before 8.5.12G (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6534 and fix it if it is affected.

What it is: CVE-2016-6534 is a high-severity command injection vulnerability in Opmantek NMIS before 8.5.12G, published on 10 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-6534 in the wild and no public exploit code.

Affected product: Opmantek NMIS before 8.5.12G. 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-2016-6534/ (Markdown: https://insights.sbomify.com/CVE-2016-6534/index.md)
```

## Sources

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

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