CVE-2013-7030

HIGHNVD 7.37.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.3 from GitHub Security Advisory published 2022-05-17. NVD baseline CVSS 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Weaponized
7.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit code is available (Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 5.2%CVSS: 7.3Exploit: Exploit-DB (verified)Exposed services: Not assessed

No fix has been recorded since the CVE record was published in 2013 — if the vendor still supports the product, apply the fixed version it names; if not, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

The TFTP service in Cisco Unified Communications Manager (aka CUCM or Unified CM) allows remote attackers to obtain sensitive information from a phone via an RRQ operation, as demonstrated by discovering a cleartext UseUserCredential field in an SPDefault.cnf.xml file. NOTE: the vendor reportedly disputes the significance of this report, stating that this is an expected default behavior, and that the product's documentation describes use of the TFTP Encrypted Config option in addressing this issue

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
59
EG Risk 59/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)
Severity73% × 45%
The EG Score, 7.3 of 10.
Exploitation65% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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 2013. If the vendor still supports the product, apply the fixed version it names within your standard update timelines; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.
EPSS PROB
5.2%
EPSS %ILE
92nd
KEV
Not listed

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

No fix has been recorded since the CVE record was published in 2013. If the vendor still supports the product, apply the fixed version it names within your standard update timelines; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 12, 2013

Last Modified

April 29, 2026

Advisory Details (2)

Auto-updated Apr 30, 2026
No fix on record since 2013.
Web page

IBM X-Force Exchange

https://exchange.xforce.ibmcloud.com/vulnerabilities/89649
Web page

Cisco Unified Communications Manager - TFTP Service - Hardware local Exploit

http://www.exploit-db.com/exploits/30237/

Data Freshness Timeline

(refreshed 9× in last 7d / 20× 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 85 of 127 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. 15 repeat rows among the latest 100 are merged into the row they repeat. The 42 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). No fix has been recorded since the CVE record was published in 2013. If the vendor still supports the product, apply the fixed version it names; if it no longer does, isolate the affected system or retire the product.

  • Exploit-DBEDB-30237✓ verified
    Published Dec 12, 2013

    Cisco Unified Communications Manager - TFTP Service

    Open source ↗

Frequently asked(5)

What is CVE-2013-7030?
CVE-2013-7030 is a high-severity vulnerability; its CVE record was published on December 12, 2013. The TFTP service in Cisco Unified Communications Manager (aka CUCM or Unified CM) allows remote attackers to obtain sensitive information from a phone via an RRQ operation, as demonstrated by discovering a cleartext UseUserCredential field in an SPDefault.cnf.xml file. NOTE: the vendor reportedly…
When was CVE-2013-7030 made public?
CVE-2013-7030 was made public on December 12, 2013: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on December 12, 2013. EchelonGraph's copy of the record carries a last-modified date of April 29, 2026; the record at its source may have been updated since.
Is CVE-2013-7030 actively exploited?
CVE-2013-7030 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 5.2% probability of exploitation in the next 30 days (92nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2013-7030?
CVE-2013-7030 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2013-7030?
No fix for CVE-2013-7030 has been recorded since its CVE record was published in 2013. If the vendor still supports the product, apply the fixed version it names; if it no longer does, 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-2013-7030

Explore →

Is Your Infrastructure Affected by CVE-2013-7030?

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

Book a Demo →Browse All CVEs