[Full-disclosure] [MU-200807-01] Remote DoS in reSIProcate

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Remote DoS in reSIProcate [MU-200807-01]
July 10, 2008

http://labs.mudynamics.com/advisories.html


Affected Products/Versions:

* repro SIP proxy/registrar 1.3.2
http://www.resiprocate.org/ReSIProcate_1.3.2_Release

* Any product using the reSIProcate SIP stack 1.3.2 may also be vulnerable.


Product Overview:

http://www.resiprocate.org/

reSIProcate is a SIP stack. SIP is a protocol used for voice-over-IP
telephony. repro is a SIP proxy/registrar that uses the reSIProcate SIP stack.


Vulnerability Details:

A malformed INVITE or OPTIONS message to the repro SIP proxy/registrar can
crash the process. The crash is caused by an assertion failure that occurs
when the domain name in the request line URI is too long
(rutil/dns/DnsStub.cxx, line 493). For example, the URI may be
"sip:bob@xxxxxxxxxxxxxxxxxxxxx", where "sip:bob@xxxxxxxxxxx" is followed by
256 As. To cause the crash, the address in the To header must be a valid
target address.

Example invalid packet:
OPTIONS sip:bob@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:54422;branch=z9hG4bKZqPsHMEiem;rport
To: "Bob" <sip:bob@xxxxxxxxxxx>
From: "Alice" <sip:alice@xxxxxxxxxxx>;tag=W4eHvLYEQX
Call-ID: nO1DpTVfo4@xxxxxxxxxxxxxx
CSeq: 1 OPTIONS
Contact: <sip:alice@xxxxxxxxx:54422>
Max-Forwards: 70
Content-Length: 0


Vendor Response / Solution:

Update to 1.3.3, available from
https://www.resiprocate.org/files/pub/reSIProcate/releases/

This bug was also fixed by the reSIProcate development team in SVN on
April 23 (revision 7628).


History:

July 1, 2008 - First contact with vendor
July 1, 2008 - Vendor acknowledges vulnerability
July 3, 2008 - Vendor releases 1.3.3
July 10, 2008 - Advisory released


Mu-4000 vector:

*.request-line.line.dsv.uri.body.string.append-overflow


Credit:

This vulnerability was discovered by the Mu Dynamics research team.

http://labs.mudynamics.com/pgpkey.txt

Mu Dynamics offers a new class of security analysis system, delivering a
rigorous and streamlined methodology for verifying the robustness and security
readiness of any IP-based product or application. Founded by the pioneers of
intrusion detection and prevention technology, Mu Dynamics is backed by
preeminent venture capital firms that include Accel Partners, Benchmark
Capital and DAG Ventures. The company is headquartered in Sunnyvale, CA. For
more information, visit the company's website at http://www.mudynamics.com.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iD8DBQFIdqOZQLdDlEyOXHQRAvt+AJsHGgqEVoiQi0Nb7ND9CR7HteZJpgCeMgKv
5lqpYSLdj7WBeXoD4l95+WA=
=KUQC
-----END PGP SIGNATURE-----

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

Relevant Pages

  • TSP and ReSIProcate
    ... I’m trying to build TSP for SIP protocol. ... It’s a education project and I have some problems with linking TAPI part which I’ve created with Julmar’s TSP ++ and ReSIProcate SIP stack. ... I’ve made .cpp and .h files for my sip register function in my TSP and compiling went without errors. ...
    (microsoft.public.win32.programmer.tapi)
  • Re: [Full-disclosure] CISCO Phone 7940 DOS vulnerability
    ... We are always open for vulnerability reports regarding any Cisco ... Cisco 7940 SIP INVITE remote DOS ... using the Madynes VoIP fuzzer. ... This vulnerability was identified by the Madynes research team at INRIA ...
    (Full-Disclosure)
  • [VulnWatch] Asterisk SIP Implementation Issue
    ... Advisory Name: Asterisk SIP Implementation Issue ... @stake found a vulnerability that could allow an attacker ... This is a good example of a vulnerability that would be difficult to ...
    (VulnWatch)
  • [Full-disclosure] Nokia N95 cellphone remote DoS using the SIP Stack
    ... Nokia N95 cellphone remote DoS using the SIP Stack ... that trigger the vulnerability of the target. ...
    (Full-Disclosure)
  • WengoPhone SIP phone Remote Denial of Service vulnerability
    ... WengoPhone SIP phone Remote Denial of Service vulnerability ... It is a free and wild used SIP based softphone. ... A message validation check flaw in WengoPhone SIP phone implementation may allow a remote attacker to crash the phone causing denial of service. ... unsigned long resolv(const char *host) ...
    (Bugtraq)