Vulnerability Note VU#521252

Integer overflow vulnerability in Asterisk driver for Cisco SCCP-enabled phones

Original Release date: 24 Oct 2006 | Last revised: 19 Jan 2007


Asterisk contains an integer overflow vulnerability. This vulnerability may allow an attacker to run arbitrary code.


Asterisk is an open-source PBX software package that provides voicemail, three-way calling, and other features. Skinny Client Control Protocol (SCCP) is a proprietary Cisco protocol that is used to connect Cisco Call Managers and Cisco Voice over IP (VOIP) phones. Asterisk provides a driver for phones that use the SCCP protocol called chan_skinny.

An integer overflow vulnerability exists in the get_input(struct skinnysession *s) function which is found in the chan_skinny driver. Exploitation of this vulnerability may allow an attacker to execute arbitrary code.

Note that the chan_skinny driver only needs to be installed and loaded for a system to be vulnerable.


A remote, unauthenticated attacker may be able to execute arbitrary code with root privileges.


The Asterisk Development Team has released an update to address this issue. See Asterisk update 1.2.13 and 1.0.12 for more details.

Restrict access
Restricting network access to port 2000/tcp on the Asterisk server may limit exposure to this vulnerability.

Do not load unnecessary drivers
Adding noload=> to the modules.conf file will prevent the vulnerable driver from loading at startup time.

Systems Affected (Learn More)

VendorStatusDate NotifiedDate Updated
AsteriskAffected-24 Oct 2006
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A



This vulnerability report was based on information from Adam Boileau of

This document was written by Ryan Giobbi.

Other Information

  • CVE IDs: CVE-2006-5444
  • Date Public: 18 Oct 2006
  • Date First Published: 24 Oct 2006
  • Date Last Updated: 19 Jan 2007
  • Severity Metric: 3.82
  • Document Revision: 40


If you have feedback, comments, or additional information about this vulnerability, please send us email.