CVE-2017-17090

HIGHNVD 7.58.9▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.9 because EPSS predicts 82% probability of exploitation within the next 30 days (top 0.4% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
8.9EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 82%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 82%CVSS: 7.5Exploit: Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

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

An issue was discovered in chan_skinny.c in Asterisk Open Source 13.18.2 and older, 14.7.2 and older, and 15.1.2 and older, and Certified Asterisk 13.13-cert7 and older. If the chan_skinny (aka SCCP protocol) channel driver is flooded with certain requests, it can cause the asterisk process to use excessive amounts of virtual memory, eventually causing asterisk to stop processing requests of any kind.

CVSS v3
7.5
EG Score
8.9(high)
EG Risk
77(Track)
EG Risk 77/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
Severity89% × 45%
Exploitation82% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
82%
EPSS %ILE
100%
KEV
Not listed

Published

December 2, 2017

Last Modified

June 17, 2026

References (14)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 18× 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.

  1. 2026-07-26 14:51 UTCEPSS rescore
  2. 2026-07-25 14:13 UTCEPSS rescore
  3. 2026-07-23 01:28 UTCEG score recompute▲ 1.40
  4. 2026-07-22 22:07 UTCEG score recompute
  5. 2026-07-22 14:04 UTCEPSS rescore
  6. 2026-07-20 17:04 UTCEPSS rescore
  7. 2026-07-20 17:04 UTCEPSS rescore
  8. 2026-07-16 16:59 UTCEPSS rescore
  9. 2026-07-16 16:59 UTCEPSS rescore
  10. 2026-07-15 16:54 UTCEPSS rescore
  11. 2026-07-15 16:54 UTCEPSS rescore
  12. 2026-07-13 22:26 UTCEPSS rescore
  13. 2026-07-11 14:22 UTCOSV refresh
  14. 2026-07-11 08:24 UTCEPSS rescore
  15. 2026-07-09 19:06 UTCEPSS rescore
  16. 2026-07-04 06:28 UTCEPSS rescore
  17. 2026-07-01 15:02 UTCEPSS rescore
  18. 2026-07-01 15:02 UTCEPSS rescore
  19. 2026-06-25 13:47 UTCEPSS rescore
  20. 2026-06-25 13:47 UTCEPSS rescore
  21. 2026-06-24 14:02 UTCEPSS rescore
  22. 2026-06-23 21:30 UTCEPSS rescore
  23. 2026-06-22 21:05 UTCOSV refresh
  24. 2026-06-21 01:57 UTCEPSS rescore
  25. 2026-06-21 01:57 UTCEPSS rescore
Show 36 more
  1. 2026-06-17 17:50 UTCEPSS rescore
  2. 2026-06-16 17:50 UTCEPSS rescore
  3. 2026-06-15 17:45 UTCEPSS rescore
  4. 2026-06-12 23:09 UTCEPSS rescore
  5. 2026-06-11 13:57 UTCEPSS rescore
  6. 2026-06-10 22:15 UTCEPSS rescore
  7. 2026-06-08 14:14 UTCEPSS rescore
  8. 2026-06-07 15:22 UTCEPSS rescore
  9. 2026-06-07 15:22 UTCEPSS rescore
  10. 2026-06-06 13:45 UTCEPSS rescore
  11. 2026-06-06 13:45 UTCEPSS rescore
  12. 2026-06-05 22:44 UTCEPSS rescore
  13. 2026-06-05 11:57 UTCOSV refresh
  14. 2026-06-05 06:08 UTCEPSS rescore
  15. 2026-06-05 06:08 UTCEPSS rescore
  16. 2026-06-04 13:10 UTCEPSS rescore
  17. 2026-06-04 13:10 UTCEPSS rescore
  18. 2026-06-02 20:11 UTCEPSS rescore
  19. 2026-06-02 20:11 UTCEPSS rescore
  20. 2026-06-01 13:49 UTCEPSS rescore
  21. 2026-06-01 13:49 UTCEPSS rescore
  22. 2026-05-31 22:28 UTCEPSS rescore
  23. 2026-05-31 00:14 UTCEPSS rescore
  24. 2026-05-27 13:38 UTCEPSS rescore
  25. 2026-05-27 13:38 UTCEPSS rescore
  26. 2026-05-22 21:15 UTCEPSS rescore
  27. 2026-05-22 21:15 UTCEPSS rescore
  28. 2026-05-22 21:15 UTCEPSS rescore
  29. 2026-05-22 07:34 UTCEG score recompute
  30. 2026-05-22 07:33 UTCGHSA enrichment
  31. 2026-05-20 22:37 UTCEPSS rescore
  32. 2026-05-20 22:37 UTCEPSS rescore
  33. 2026-05-20 11:21 UTCEPSS rescore
  34. 2026-05-20 11:21 UTCEPSS rescore
  35. 2026-05-18 21:30 UTCEPSS rescore
  36. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-43992✓ verified
    First seen Feb 7, 2018

    Asterisk 13.17.2 - 'chan_skinny' Remote Memory Corruption

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2017-17090?
CVE-2017-17090 is a high vulnerability published on December 2, 2017. An issue was discovered in chanskinny.c in Asterisk Open Source 13.18.2 and older, 14.7.2 and older, and 15.1.2 and older, and Certified Asterisk 13.13-cert7 and older. If the chanskinny (aka SCCP protocol) channel driver is flooded with certain requests, it can cause the asterisk process to use…
When was CVE-2017-17090 disclosed?
CVE-2017-17090 was first published in the National Vulnerability Database on December 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-17090 actively exploited?
CVE-2017-17090 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 82% probability of exploitation in the next 30 days, which ranks it in the top 0.4% of all scored CVEs.
What is the CVSS score of CVE-2017-17090?
CVE-2017-17090 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.9.
How do I remediate CVE-2017-17090?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-17090, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2017-17090?

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

Start Free Scan →Browse All CVEs