CVE-2017-14099

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 4%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In res/res_rtp_asterisk.c in Asterisk 11.x before 11.25.2, 13.x before 13.17.1, and 14.x before 14.6.1 and Certified Asterisk 11.x before 11.6-cert17 and 13.x before 13.13-cert5, unauthorized data disclosure (media takeover in the RTP stack) is possible with careful timing by an attacker. The "strictrtp" option in rtp.conf enables a feature of the RTP stack that learns the source address of media for a session and drops any packets that do not originate from the expected address. This option is enabled by default in Asterisk 11 and above. The "nat" and "rtp_symmetric" options (for chan_sip and chan_pjsip, respectively) enable symmetric RTP support in the RTP stack. This uses the source address of incoming media as the target address of any sent media. This option is not enabled by default, but is commonly enabled to handle devices behind NAT. A change was made to the strict RTP support in the RTP stack to better tolerate late media when a reinvite occurs. When combined with the symmetric RTP support, this introduced an avenue where media could be hijacked. Instead of only learning a new address when expected, the new code allowed a new source address to be learned at all times. If a flood of RTP traffic was received, the strict RTP support would allow the new address to provide media, and (with symmetric RTP enabled) outgoing traffic would be sent to this new address, allowing the media to be hijacked. Provided the attacker continued to send traffic, they would continue to receive traffic as well.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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
Severity75% × 45%
Exploitation4% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
4%
EPSS %ILE
91%
KEV
Not listed

Published

September 2, 2017

Last Modified

June 17, 2026

References (14)

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
asterisk—1:13.17.1~dfsg-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
asterisk0.1.11-3 ... 1:13.9.1~dfsg-2 (213 versions)1:13.17.1~dfsg-1—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
asterisk1:11.13.1~dfsg-2, 1:11.13.1~dfsg-2+deb8u1, 1:11.13.1~dfsg-2+deb8u21:11.13.1~dfsg-2+deb8u3—
Debian:9(1)
PackageVulnerable rangeFixed inDependents
asterisk1:13.14.1~dfsg-21:13.14.1~dfsg-2+deb9u1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 132 total refreshes for this CVE.

  1. 2026-09-07 15:56 UTCEPSS rescore
  2. 2026-09-04 13:56 UTCEPSS rescore
  3. 2026-09-04 05:01 UTCEPSS rescore
  4. 2026-09-02 14:07 UTCEPSS rescore
  5. 2026-09-01 13:48 UTCEPSS rescore
  6. 2026-09-01 03:31 UTCEPSS rescore
  7. 2026-08-30 19:13 UTCEPSS rescore
  8. 2026-08-30 07:00 UTCOSV refresh
  9. 2026-08-28 21:36 UTCEPSS rescore
  10. 2026-08-27 14:20 UTCEPSS rescore
  11. 2026-08-26 14:41 UTCEPSS rescore
  12. 2026-08-25 13:44 UTCEPSS rescore
  13. 2026-08-24 14:10 UTCEPSS rescore
  14. 2026-08-21 23:44 UTCEPSS rescore
  15. 2026-08-20 22:50 UTCEPSS rescore
  16. 2026-08-19 16:59 UTCEPSS rescore
  17. 2026-08-18 13:43 UTCEPSS rescore
  18. 2026-08-17 13:42 UTCEPSS rescore
  19. 2026-08-16 14:51 UTCEPSS rescore
  20. 2026-08-16 02:10 UTCEPSS rescore
  21. 2026-08-15 01:26 UTCEPSS rescore
  22. 2026-08-13 22:44 UTCOSV refresh
  23. 2026-08-13 21:56 UTCEPSS rescore
  24. 2026-08-09 13:42 UTCEPSS rescore
  25. 2026-08-08 16:32 UTCEPSS rescore
Show 75 more
  1. 2026-08-07 16:22 UTCEPSS rescore
  2. 2026-08-06 13:42 UTCEPSS rescore
  3. 2026-08-05 19:12 UTCEPSS rescore
  4. 2026-08-04 15:05 UTCEPSS rescore
  5. 2026-08-04 10:32 UTCEPSS rescore
  6. 2026-08-03 10:30 UTCEPSS rescore
  7. 2026-08-02 02:23 UTCEPSS rescore
  8. 2026-08-01 04:11 UTCEPSS rescore
  9. 2026-07-30 16:24 UTCEPSS rescore
  10. 2026-07-30 01:26 UTCEPSS rescore
  11. 2026-07-29 01:47 UTCOSV refresh
  12. 2026-07-28 15:32 UTCEPSS rescore
  13. 2026-07-25 14:13 UTCEPSS rescore
  14. 2026-07-23 14:15 UTCEPSS rescore
  15. 2026-07-23 01:27 UTCEG score recompute
  16. 2026-07-22 22:06 UTCEG score recompute
  17. 2026-07-22 14:04 UTCEPSS rescore
  18. 2026-07-21 15:21 UTCEPSS rescore
  19. 2026-07-21 15:21 UTCEPSS rescore
  20. 2026-07-20 17:04 UTCEPSS rescore
  21. 2026-07-20 17:04 UTCEPSS rescore
  22. 2026-07-19 14:28 UTCEPSS rescore
  23. 2026-07-19 14:28 UTCEPSS rescore
  24. 2026-07-19 02:26 UTCEPSS rescore
  25. 2026-07-19 02:26 UTCEPSS rescore
  26. 2026-07-18 10:00 UTCEPSS rescore
  27. 2026-07-16 16:59 UTCEPSS rescore
  28. 2026-07-16 16:59 UTCEPSS rescore
  29. 2026-07-15 16:54 UTCEPSS rescore
  30. 2026-07-15 16:54 UTCEPSS rescore
  31. 2026-07-15 01:56 UTCEPSS rescore
  32. 2026-07-13 22:26 UTCEPSS rescore
  33. 2026-07-13 06:09 UTCEPSS rescore
  34. 2026-07-12 05:43 UTCEPSS rescore
  35. 2026-07-11 18:22 UTCOSV refresh
  36. 2026-07-11 08:24 UTCEPSS rescore
  37. 2026-07-09 19:06 UTCEPSS rescore
  38. 2026-07-08 15:10 UTCEPSS rescore
  39. 2026-07-07 13:42 UTCEPSS rescore
  40. 2026-07-06 16:24 UTCEPSS rescore
  41. 2026-07-06 02:20 UTCEPSS rescore
  42. 2026-07-05 02:27 UTCEPSS rescore
  43. 2026-07-04 06:28 UTCEPSS rescore
  44. 2026-07-01 15:02 UTCEPSS rescore
  45. 2026-07-01 15:02 UTCEPSS rescore
  46. 2026-06-30 23:19 UTCEPSS rescore
  47. 2026-06-30 23:19 UTCEPSS rescore
  48. 2026-06-29 14:03 UTCEPSS rescore
  49. 2026-06-28 14:04 UTCEPSS rescore
  50. 2026-06-28 04:53 UTCEPSS rescore
  51. 2026-06-27 03:05 UTCEPSS rescore
  52. 2026-06-25 13:47 UTCEPSS rescore
  53. 2026-06-25 13:47 UTCEPSS rescore
  54. 2026-06-24 14:02 UTCEPSS rescore
  55. 2026-06-23 21:30 UTCEPSS rescore
  56. 2026-06-23 01:00 UTCOSV refresh
  57. 2026-06-21 14:54 UTCEPSS rescore
  58. 2026-06-21 14:54 UTCEPSS rescore
  59. 2026-06-21 01:57 UTCEPSS rescore
  60. 2026-06-21 01:57 UTCEPSS rescore
  61. 2026-06-19 19:23 UTCEPSS rescore
  62. 2026-06-19 19:23 UTCEPSS rescore
  63. 2026-06-18 17:50 UTCEPSS rescore
  64. 2026-06-17 17:50 UTCEPSS rescore
  65. 2026-06-16 17:50 UTCEPSS rescore
  66. 2026-06-15 17:45 UTCEPSS rescore
  67. 2026-06-14 23:14 UTCEPSS rescore
  68. 2026-06-14 23:14 UTCEPSS rescore
  69. 2026-06-13 22:57 UTCEPSS rescore
  70. 2026-06-12 23:09 UTCEPSS rescore
  71. 2026-06-11 13:57 UTCEPSS rescore
  72. 2026-06-10 22:15 UTCEPSS rescore
  73. 2026-06-08 14:14 UTCEPSS rescore
  74. 2026-06-07 15:22 UTCEPSS rescore
  75. 2026-06-07 15:22 UTCEPSS rescore

Frequently asked(5)

What is CVE-2017-14099?
CVE-2017-14099 is a high vulnerability published on September 2, 2017. In res/resrtpasterisk.c in Asterisk 11.x before 11.25.2, 13.x before 13.17.1, and 14.x before 14.6.1 and Certified Asterisk 11.x before 11.6-cert17 and 13.x before 13.13-cert5, unauthorized data disclosure (media takeover in the RTP stack) is possible with careful timing by an attacker. The…
When was CVE-2017-14099 disclosed?
CVE-2017-14099 was first published in the National Vulnerability Database on September 2, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-14099 actively exploited?
CVE-2017-14099 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4% probability of exploitation in the next 30 days, which ranks it in the top 9.5% of all scored CVEs.
What is the CVSS score of CVE-2017-14099?
CVE-2017-14099 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2017-14099?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-14099, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-14099

Explore →

Is Your Infrastructure Affected by CVE-2017-14099?

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

Start Free Scan →Browse All CVEs