CVE-2016-6534
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpmantek 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCommand injection vulnerability in Opmantek NMIS tools.pl CGI script allows remote attackers to execute arbitrary OS commands via the man, finger, ping, trace, or nslookup parameters without proper input sanitization, leveraging unsanitized user input passed to system shell execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 4.3.6f<= 8.5.10gCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate NMIS installationSearch for the NMIS directory structure on the system, typically installed in /usr/local/nmis, /opt/nmis, or similar locations. Look for directories containing 'nmis' in the name.Affected if NMIS software is installed on the system
-
Identify NMIS versionCheck the version file or configuration within the NMIS installation directory. Common locations include version.info, NMIS.pm, or the admin interface version display.Affected if Installed version is 4.3.6f or earlier, OR 8.5.10g or earlier
-
Find tools.pl CGI scriptLocate the tools.pl file within the NMIS web directory, commonly in cgi-bin/ or nmis/cgi/ subdirectories under the web root.Affected if The tools.pl script exists in the web-accessible cgi-bin directory
-
Verify web accessibilityDetermine if the tools.pl script is accessible via HTTP/HTTPS from the web server configuration. Check the web server (Apache, nginx, etc.) configuration for cgi-bin or alias directives exposing this script.Affected if The tools.pl script is accessible over the network via web server
User is affected if NMIS is installed with version 4.3.6f or earlier (or 8.5.10g or earlier) AND the tools.pl CGI script is present and web-accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to NMIS version 4.3.7c or later (8.5.12G for newer branches). If immediate patching is unavailable, restrict or disable access to the tools.pl CGI script at the web server level.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6534 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-6534 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data