Skip to content
Fencer Intel
high 7.5

CVE-2017-17090 in the critical feed json

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 A…

published 2017-12-02 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-8256

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
82.2%
EPSS 82.2% chance of exploitation in 30 days, percentile 99.6%
public exploits
1
Exploit-DB

Summary

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.

Patch / fix

  • asterisk Debian 14 1:13.18.3~dfsg-1

debian advisories DEBIAN-CVE-2017-17090

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-17090 updated cvss 7.5

asterisk: DOS Vulnerability in Asterisk chan_skinny

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. Published
  2. First public exploit (EDB-43992)

Exploit prediction

82.20% chance of exploitation in the next 30 days, higher than 99.6% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-43992 Asterisk 13.17.2 - 'chan_skinny' Remote Memory Corruption dos, 2018-02-07

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.