Asterisk BYE/Also transfer method denial of service
| asterisk-bye-also-dos (39361) |
Description:
Asterisk is vulnerable to a denial of service, caused by a NULL pointer dereference in the handling of the BYE with Also transfer method. If a dialog has already been established, a remote attacker could attempt to make a transfer using the BYE message and crash the vulnerable application.
Platforms Affected:
- Digium, Asterisk Appliance Developer Kit SVN - 1.4 rev. 95946
- Digium, Asterisk Business Edition C.x.x prior to C.1.0-b8
- Digium, Asterisk Open Source 1.4.x prior to 1.4.17
- Digium, AsteriskNOW pre-release -beta7
- Digium, s800i 1.0.x - 1.0.3.4
Remedy:
Refer to AST-2008-001 for patch, upgrade, or suggested workaround information. See References.
Consequences:
Denial of Service
References:
- AST-2008-001, Remote Crash Vulnerability in SIP channel driver at http://downloads.digium.com/pub/security/AST-2008-001.pdf.
- BID-27110: Asterisk BYE Message Remote Denial of Service Vulnerability
- CVE-2008-0095: The SIP channel driver in Asterisk Open Source 1.4.x before 1.4.17, Business Edition before C.1.0-beta8, AsteriskNOW before beta7, Appliance Developer Kit before Asterisk 1.4 revision 95946, and Appliance s800i 1.0.x before 1.0.3.4 allows remote attackers to cause a denial of service (daemon crash) via a BYE message with an Also (Also transfer) header, which triggers a NULL pointer dereference.
- SA28312: Asterisk "BYE/Also" Denial of Service Vulnerability
- SECTRACK ID: 1019152: Asterisk SIP Channel Driver Can Be Crashed By Remote Users With 'BYE with Also' Method
- VUPEN/ADV-2008-0019: Asterisk SIP Channel Driver BYE Message Denial of Service Vulnerability
Reported:
Jan 02, 2008
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net
