dbcve.org
Emergency ResponderApplication · Cisco

CVE-2017-6779

HIGH · 7.5 CVSS v3.0 Published 2018-06-07
Fix available
A fix is available. Upgrade to 10.5 / 10.5.2 or later.
See remediation →
84/100
Remediation priority · High
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
Multiple Cisco products are affected by a vulnerability in local file management for certain system log files of Cisco collaboration products that could allow an unauthenticated, remote attacker to cause high disk utilization, resulting in a denial of service (DoS) condition. The vulnerability occurs because a certain system log file does not have a maximum size restriction. Therefore, the file is allowed to consume the majority of available disk space on the appliance. An attacker could exploit this vulnerability by sending crafted remote connection requests to the appliance. Successful exploitation could allow the attacker to increase the size of a system log file so that it consumes most of the disk space. The lack of available disk space could lead to a DoS condition in which the application functions could operate abnormally, making the appliance unstable. This vulnerability affects the following Cisco Voice Operating System (VOS)-based products: Emergency Responder, Finesse, Hosted Collaboration Mediation Fulfillment, MediaSense, Prime License Manager, SocialMiner, Unified Communications Manager (UCM), Unified Communications Manager IM and Presence Service (IM&P - earlier releases were known as Cisco Unified Presence), Unified Communication Manager Session Management Edition (SME), Unified Contact Center Express (UCCx), Unified Intelligence Center (UIC), Unity Connection, Virtualized Voice Browser. This vulnerability also affects Prime Collaboration Assurance and Prime Collaboration Provisioning. Cisco Bug IDs: CSCvd10872, CSCvf64322, CSCvf64332, CSCvi29538, CSCvi29543, CSCvi29544, CSCvi29546, CSCvi29556, CSCvi29571, CSCvi31738, CSCvi31741, CSCvi31762, CSCvi31807, CSCvi31818, CSCvi31823.

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

A vulnerability exists in multiple Cisco Voice Operating System (VOS)-based collaboration products where a certain system log file lacks a maximum size restriction. An unauthenticated, remote attacker can exploit this by sending crafted remote connection requests to cause the log file to grow unbounded and consume the majority of available disk space, resulting in a denial of service condition where application functions become unstable.

MitigationImplement log rotation or file size limits for the affected system log files to prevent unbounded growth. Monitor disk usage and consider network-level controls to limit suspicious connection requests.

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
Emergency ResponderApplication
Affected:>= 10.5, < 10.5\(1a\)>= 11.0, < 11.5\(4\)>= 12.0, < 12.0su1= 11.0\(1.10000.10\)
FinesseApplication
Affected:>= 11.5, < 11.5\(3\)= 9.5\(1\)
Hosted Collaboration Mediation FulfillmentApplication
Affected:>= 11.5, < 11.5\(3\)= 9.5\(1\)
MediasenseApplication
Affected:>= 11.5, < 11.5su2= 9.5\(1\)
Prime Collaboration AssuranceApplication
Affected:>= 11.6, < 11.6_es16>= 12.1, < 12.1_es2
Prime Collaboration ProvisioningApplication
Affected:= 12.5
Prime License ManagerApplication
Affected:>= 10.5, < 10.5.2>= 11.0, < 11.5\(1\)su5
SocialminerApplication
Affected:>= 11.6, < 11.6.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
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the Cisco VOS product and version
    Access the product admin interface or run 'show version' via CLI to determine the installed product name and exact version number
    Affected if The product is one of: Cisco Emergency Responder, Cisco Finesse, Cisco Hosted Collaboration Mediation Fulfillment, Cisco Mediasense, Cisco Prime Collaboration Assurance, Cisco Prime Collaboration Provisioning, Cisco Prime License Manager, or Cisco Socialminer, and the version falls within the affect
  2. Verify the version is within affected ranges
    Compare your installed version against the affected version list for your specific product. For example, Cisco Finesse is affected if version is >= 11.5 and < 11.5(3), or exactly 9.5(1)
    Affected if The installed version matches any of the vulnerable version ranges specified in the CVE for that product
  3. Locate the system log file
    Access the VOS platform and identify the system log file that lacks size restrictions. Typically found in /var/log/ or platform-specific log directories used by the collaboration application
    Affected if A system log file exists and is present on the system without configured size limits or rotation policies
  4. Check for log file size limits or rotation
    Examine the log configuration files (such as logging configuration, logrotate settings, or platform-specific configuration) to determine if maximum size restrictions are defined for the system log file
    Affected if No maximum size limit or log rotation is configured for the vulnerable system log file
  5. Assess disk space consumption by logs
    Run 'df -h' to check disk usage and 'ls -lh' on log directories to identify unusually large log files, especially the system log file referenced in the vulnerability
    Affected if The system log file has grown to consume a significant portion of available disk space, indicating the vulnerability may have been triggered

A user is affected if they are running any of the listed Cisco VOS products within the specific version ranges AND the system log file lacks maximum size restrictions, allowing unbounded growth that can cause denial of service.

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 10.5 / 10.5.2 / 11.5su2 or later
Fixed in 10.510.5.211.5su2
Interim mitigation

Implement log rotation or file size limits for the affected system log files to prevent unbounded growth. Monitor disk usage and consider network-level controls to limit suspicious connection requests.

Fix this in Emergency Responder Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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