|
|
|
|
| |
| The Asterisk STUN implementation in the RTP stack has a remotely exploitable crash vulnerability. A pointer may run past accessible memory if Asterisk receives a specially crafted STUN packet on an active RTP port. |
| |
Credit:
The information has been provided by Kevin P. Fleming.
The original article can be found at: http://ftp.digium.com/pub/asa/ASA-2007-017.pdf
|
| |
Vulnerable Systems:
* Asterisk Open Source versions prior to 1.4.8
* AsteriskNOW prerelease versions prior to Beta7
* Asterisk Appliance Developer Kit versions prior to 0.5.0
* s800i (Asterisk Appliance) versions prior to 1.0.2
Immune Systems:
* Asterisk Open Source version 1.4.8
* AsteriskNOW Beta7
* Asterisk Appliance Developer Kit version 0.5.0
* s800i (Asterisk Appliance) version 1.0.2
The code that parses the incoming STUN packets incorrectly checks that the length indicated in the STUN attribute and the size of the STUN attribute header does not exceed the available data. This will cause the data pointer to run past accessible memory and when accessed will cause a crash.
Resolution:
All users that have chan_sip, chan_gtalk, chan_jingle, chan_h323, chan_mgcp, or chan_skinny enabled on an affected version should upgrade to the appropriate version listed in the correct in section of this advisory.
|
|
|
|
|
|
|
|
|
|
