dbcve.org
Network Analysis ModuleHardware / appliance · Cisco

CVE-2016-1388

CRITICAL · 9.8 CVSS v3.0 Published 2016-06-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Cisco Prime Network Analysis Module (NAM) before 6.1(1) patch.6.1-2-final and 6.2.x before 6.2(1) and Prime Virtual Network Analysis Module (vNAM) before 6.1(1) patch.6.1-2-final and 6.2.x before 6.2(1) allow remote attackers to execute arbitrary OS commands via a crafted HTTP request, aka Bug ID CSCuy21882.

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 confidence

Cisco Prime Network Analysis Module (NAM) and Virtual NAM (vNAM) contain a command injection vulnerability in their web-based management interface. Attackers can execute arbitrary OS commands by sending specially crafted HTTP requests to the affected web service, potentially gaining full control of the underlying operating system.

MitigationApply vendor patches 6.1(1) patch.6.1-2-final or 6.2(1) and later. As an interim measure, restrict network access to the management interface using ACLs or place behind a jump host.

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 Analysis ModuleHardware / appliance
Affected:all versions
Prime Network Analysis Module SoftwarePlugin / extension
Affected:= 5.0.0= 5.0.1= 5.0.2= 5.1.0= 5.1.2= 6.0.2= 6.1.0= 6.1.1= 6.2.0
Prime Virtual Network Analysis Module SoftwarePlugin / extension
Affected:= 6.0.0= 6.1.0= 6.2.0

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 checks

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

  1. Identify if Cisco NAM or vNAM is installed
    Locate the installed product: check for 'Cisco Network Analysis Module', 'Prime NAM', or 'vNAM' in installed software lists, or check running services on the device for NAM-related processes. On the device CLI, use 'show version' or check the web interface login page for product identification.
    Affected if The product is Cisco Network Analysis Module, Cisco Prime Network Analysis Module Software, or Cisco Prime Virtual Network Analysis Module Software.
  2. Determine the installed software version
    Access the web-based management interface and look at the version displayed on the login page or in the About/Help section. Alternatively, via CLI use 'show version' or 'show software' commands to retrieve the exact version number.
    Affected if The installed version matches: 5.0.0, 5.0.1, 5.0.2, 5.1.0, 5.1.2, 6.0.2, 6.1.0, 6.1.1, 6.2.0 (for Prime NAM) or 6.0.0, 6.1.0, 6.2.0 (for vNAM) OR if using legacy Cisco Network Analysis Module with all versions and unpatched.
  3. Verify the web-based management interface is enabled
    Check if the HTTP/HTTPS service for the NAM web interface is running and accessible. Use 'show service' or check network listening ports (typically 80/443 or 8080/8443) on the NAM device.
    Affected if The web management interface service is active and reachable.
  4. Confirm network accessibility of the management interface
    Determine if the web interface is exposed to network segments beyond trusted administration networks. Check ACLs, firewall rules, or interface bindings. Attempt to reach the web interface from an untrusted network segment or verify that external access is permitted.
    Affected if The NAM web management interface is accessible from network segments that are not restricted to trusted administrators.

You are affected if Cisco NAM or vNAM is installed with an unpatched version (5.0.0-6.2.0 range) and the web-based management interface is network-accessible.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches 6.1(1) patch.6.1-2-final or 6.2(1) and later. As an interim measure, restrict network access to the management interface using ACLs or place behind a jump host.

Recommended fix High confidence

6.1(1) patch.6.1-2-final or 6.2(1) (depending on target branch)

  1. Identify the current version of Cisco Prime Network Analysis Module (NAM) or Prime Virtual Network Analysis Module (vNAM) by accessing the admin interface or using CLI
  2. Determine the current version branch: versions 5.x and 6.0.x/6.1.x should target 6.1(1) patch.6.1-2-final; version 6.2.x should target 6.2(1)
  3. Download the appropriate patched software image from Cisco's official download site (tools.cisco.com) for the target version
  4. Back up the current device configuration before initiating the upgrade
  5. Upload the new software image to the NAM/vNAM device using the management interface or SCP/FTP
  6. Initiate the upgrade following Cisco's standard upgrade procedure for the specific platform
  7. Verify the upgrade completed successfully and confirm the device is running the patched version (6.1(1) patch.6.1-2-final or 6.2(1) or later)
  8. Validate the vulnerability is remediated by confirming the patch level

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Network Analysis Module Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1388 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-1388 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