CVE-2017-6779

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.0%CVSS: 7.5Exploit: None knownExposed services: Not assessed

No fix has been recorded since the CVE record was published in 2018 — isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
50
EG Risk 50/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix has been recorded since the CVE record was published in 2018. Isolate the affected system within your standard update timelines at low or medium mission impact and sooner than that at high (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.
EPSS PROB
2.0%
EPSS %ILE
80th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix has been recorded since the CVE record was published in 2018. Isolate the affected system within your standard update timelines at low or medium mission impact and sooner than that at high (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

Published

June 7, 2018

Last Modified

July 31, 2025

References (1)

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 23× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 81 of 135 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 19 repeat rows among the latest 100 are merged into the row they repeat. The 54 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 13:41 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  2. 2026-10-10 19:55 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  3. 2026-10-09 20:02 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  4. 2026-10-08 16:36 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  5. 2026-10-07 23:41 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  6. 2026-10-06 15:12 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  7. 2026-10-05 17:39 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  8. 2026-10-04 23:18 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  9. 2026-10-03 14:21 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  10. 2026-09-30 14:59 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  11. 2026-09-30 09:37 UTCEG score recompute
  12. 2026-09-28 13:45 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  13. 2026-09-27 13:40 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  14. 2026-09-26 15:53 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  15. 2026-09-26 00:19 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  16. 2026-09-24 13:59 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  17. 2026-09-23 13:42 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  18. 2026-09-21 20:27 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  19. 2026-09-20 20:09 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  20. 2026-09-19 15:36 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  21. 2026-09-17 19:22 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  22. 2026-09-15 03:05 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  23. 2026-09-12 14:56 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  24. 2026-09-11 09:31 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  25. 2026-09-07 15:56 UTCEPSS rescoreEPSS 2.0% · 79th percentile
Show 56 more
  1. 2026-09-05 15:24 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  2. 2026-09-04 13:56 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  3. 2026-09-04 05:02 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  4. 2026-09-02 14:07 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  5. 2026-09-01 03:31 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  6. 2026-08-30 19:13 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  7. 2026-08-28 21:36 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  8. 2026-08-27 14:21 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  9. 2026-08-26 14:41 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  10. 2026-08-25 13:44 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  11. 2026-08-23 00:14 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  12. 2026-08-21 23:44 UTCEPSS rescoreEPSS 2.0% · 79th percentile
  13. 2026-08-19 16:59 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  14. 2026-08-18 13:43 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  15. 2026-08-16 14:51 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  16. 2026-08-16 02:10 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  17. 2026-08-15 01:26 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  18. 2026-08-12 13:46 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  19. 2026-08-08 16:32 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  20. 2026-08-07 16:22 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  21. 2026-08-06 13:42 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  22. 2026-08-05 19:13 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  23. 2026-08-02 02:23 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  24. 2026-08-01 04:12 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  25. 2026-07-30 16:24 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  26. 2026-07-30 01:26 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  27. 2026-07-28 15:32 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  28. 2026-07-26 14:51 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  29. 2026-07-23 14:15 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  30. 2026-07-23 01:30 UTCEG score recompute
  31. 2026-07-22 22:09 UTCEG score recompute
  32. 2026-07-22 14:04 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  33. 2026-07-21 15:21 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  34. 2026-07-20 17:04 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  35. 2026-07-19 14:28 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  36. 2026-07-19 02:26 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  37. 2026-07-18 10:01 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  38. 2026-07-16 16:59 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  39. 2026-07-15 16:54 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  40. 2026-07-15 01:56 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  41. 2026-07-13 22:26 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  42. 2026-07-12 05:43 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  43. 2026-07-11 08:24 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  44. 2026-07-09 19:06 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  45. 2026-07-08 15:11 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  46. 2026-07-07 13:42 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  47. 2026-07-06 16:24 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  48. 2026-07-06 02:20 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  49. 2026-07-05 02:27 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  50. 2026-07-04 06:28 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  51. 2026-07-02 16:54 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  52. 2026-07-01 15:03 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  53. 2026-06-30 23:19 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  54. 2026-06-29 14:03 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  55. 2026-06-28 14:04 UTCEPSS rescoreEPSS 2.0% · 78th percentile
  56. 2026-06-28 04:53 UTCEPSS rescoreEPSS 2.0% · 78th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2017-6779?
CVE-2017-6779 is a high-severity vulnerability; its CVE record was published on June 7, 2018. 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…
When was CVE-2017-6779 made public?
CVE-2017-6779 was made public on June 7, 2018: that is the date its CVE record's CNA, Cisco Systems, Inc., gives for when the vulnerability was made public. The CVE record itself was published on June 7, 2018. EchelonGraph's copy of the record carries a last-modified date of July 31, 2025; the record at its source may have been updated since.
Is CVE-2017-6779 actively exploited?
CVE-2017-6779 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.0% probability of exploitation in the next 30 days (80th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-6779?
CVE-2017-6779 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2017-6779?
No fix for CVE-2017-6779 has been recorded since its CVE record was published in 2018, and EchelonGraph holds no vendor advisory for it. Isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-6779

Explore →

Is Your Infrastructure Affected by CVE-2017-6779?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs