dbcve.org
Ip Interoperability And Collaboration SystemApplication · Cisco

CVE-2016-6397

CRITICAL · 9.8 CVSS v3.0 Published 2016-10-28
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
A vulnerability in the interdevice communications interface of the Cisco IP Interoperability and Collaboration System (IPICS) Universal Media Services (UMS) could allow an unauthenticated, remote attacker to modify configuration parameters of the UMS and cause the system to become unavailable. Affected Products: This vulnerability affects Cisco IPICS releases 4.8(1) to 4.10(1). More Information: CSCva46644. Known Affected Releases: 4.10(1) 4.8(1) 4.8(2) 4.9(1) 4.9(2).

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

CVE-2016-6397 is a critical authentication bypass vulnerability in Cisco IPICS Universal Media Services (UMS). The flaw resides in the interdevice communications interface and allows an unauthenticated, remote attacker to modify configuration parameters, potentially causing system unavailability. The CVSS 9.8 score reflects the critical nature of unauthenticated remote code modification capability on a core telecommunications infrastructure component.

MitigationApply Cisco-provided patches for affected releases (4.8(1) through 4.10(1)); until a patch is available, restrict network access to the UMS interdevice communications interface using firewalls or ACLs to prevent unauthorized modification attempts.

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
Ip Interoperability And Collaboration SystemApplication
Affected:= 4.8\(1\)= 4.8\(2\)= 4.9\(1\)= 4.9\(2\)= 4.10\(1\)

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 IPICS is installed
    Locate Cisco IPICS installation directories or check system services for IPICS-related processes. Common paths may include /opt/cisco/ipics or similar. Use 'ps aux' or service listings to find IPICS processes.
    Affected if Cisco IPICS software is present on the system
  2. Determine the installed version of Cisco IPICS
    Run 'show version' from the IPICS CLI, check the administrative web interface for the version, or query the installed packages if using a package manager. Compare the version number against the affected list: 4.8(1), 4.8(2), 4.9(1), 4.9(2), or 4.10(1).
    Affected if The installed version matches exactly one of: 4.8(1), 4.8(2), 4.9(1), 4.9(2), or 4.10(1)
  3. Verify if Universal Media Services (UMS) is enabled
    Access the IPICS administrative interface and check the status of the Universal Media Services component. From CLI, use commands like 'show ums status' or 'show services' to determine if UMS is running.
    Affected if Universal Media Services is enabled and running on the affected version
  4. Check network exposure of the interdevice communications interface
    Review firewall rules, ACLs, and network configuration to determine if the UMS interdevice communications port is accessible from untrusted networks. Use 'show ip interface' or check port listening status with netstat.
    Affected if The UMS interdevice communications interface is exposed to network segments beyond the trusted administrative network

You are affected if Cisco IPICS version 4.8(1), 4.8(2), 4.9(1), 4.9(2), or 4.10(1) is installed with Universal Media Services enabled and the interdevice communications 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 Cisco-provided patches for affected releases (4.8(1) through 4.10(1)); until a patch is available, restrict network access to the UMS interdevice communications interface using firewalls or ACLs to prevent unauthorized modification attempts.

Recommended fix High confidence

Cisco IPICS 4.10(2) or later

  1. 1. Identify the current Cisco IPICS version installed on the system
  2. 2. Navigate to the Cisco IPICS download page or Cisco Software Checker at tools.cisco.com
  3. 3. Locate and download Cisco IPICS version 4.10(2) or later (the fixed release that addresses CVE-2016-6397)
  4. 4. Review the release notes for upgrade prerequisites and any pre-upgrade requirements
  5. 5. Back up the current IPICS configuration before proceeding with the upgrade
  6. 6. Follow the standard Cisco IPICS upgrade procedure documented in the installation guide
  7. 7. After upgrade, verify the UMS service is operational and configuration parameters are intact
  8. 8. Confirm the vulnerability is remediated by checking the running version
Caveat Verify compatibility with existing integrations and ensure proper backup before upgrading

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

Fix this in Ip Interoperability And Collaboration System Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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