Network Management Information SystemApplication · Opmantek

CVE-2016-5642

MEDIUM · 5.4 CVSS v3.0 Published 2017-04-10
Fix available
A fix is available. Upgrade to after 8.5.10g or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Opmantek NMIS before 8.5.12G has XSS via SNMP.

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 · moderate confidence

Opmantek NMIS before version 8.5.12G contains a cross-site scripting (XSS) vulnerability that allows injection of malicious scripts through SNMP data inputs.

MitigationUpdate NMIS to version 8.5.12G or later to obtain the patched version that addresses this XSS vulnerability.

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
Network Management Information SystemApplication
Affected:<= 8.5.10g

CVSS 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
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify NMIS installation
    Locate the NMIS installation directory or check for the presence of NMIS web interface files and binaries (typically in /usr/local/nmis, /opt/nmis, or similar paths). Look for the 'nmis' command-line tool in the system PATH.
    Affected if NMIS software is installed on the system
  2. Determine installed NMIS version
    Run the command to check NMIS version, commonly 'nmis -v' or 'nmis --version', or inspect the version file in the NMIS installation directory (often named version.info, VERSION, or displayed in the web interface footer).
    Affected if The installed version is 8.5.10g or any earlier version (versions prior to 8.5.12G are affected)
  3. Verify SNMP data collection is configured
    Examine the NMIS configuration files (typically nmis.conf or similar) for SNMP-related configuration sections. Check if SNMP collectors, traps, or data inputs are enabled in the configuration.
    Affected if SNMP data collection, traps, or input modules are enabled and configured in NMIS
  4. Inspect SNMP input handling for XSS filters
    Review the SNMP input processing code or configuration to determine if input validation and XSS filtering are applied to SNMP data before display or storage. Look for sanitization routines in SNMP-related CGI or perl modules.
    Affected if SNMP data inputs are processed without proper XSS input validation or sanitization

A user is affected if Opmantek NMIS is installed with version 8.5.10g or earlier and has SNMP data collection or input features enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 8.5.10g
Interim mitigation

Update NMIS to version 8.5.12G or later to obtain the patched version that addresses this XSS vulnerability.

Fix this in Network Management Information System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-5642 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-5642 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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