[Pidgin] #7624: Pidgin crashing on incoming SIP MESSAGEs

[Pidgin]

#7624: Pidgin crashing on incoming SIP MESSAGEs
--------------------------+-------------------------------------------------
 Reporter:  jasonmgeorge  |        Owner:  seanegan
     Type:  defect        |       Status:  pending 
Milestone:                |    Component:  SIMPLE  
  Version:  2.4.1         |   Resolution:          
 Keywords:                |  
--------------------------+-------------------------------------------------
Changes (by datallah):

  * status:  new => pending


Old description:

> I'm using SIMPLE to send SIP MESSAGEs back and forth to an Openser SIP
> SERVER.   Pidgin crashes on incoming SIP MESSAGEs.  Backtrace revealed
> little other than the crash appears to come from the use of  strncmp().
> I suspect it has something to do with the format of the incoming message.
> Tracing the packets with Wireshark shows that Pidgin is responding with
> 200 OK, prior to crashing.
>
> Incoming SIP MESSAGE causing the crash below.
>
> MESSAGE sip:jason at 98.192.39.160:5062;transport=tcp SIP/2.0
> Max-Forwards: 10
> Via: SIP/2.0/TCP 192.168.1.50;branch=z9hG4bKfbe3.90b9e2e5.0
> Via: SIP/2.0/UDP 98.192.39.160:5060;branch=z9hG4bKfbe3.80b9e2e5.0
> To: sip:jason at texas.kicks-ass.org
> From: sip:chowz at texas.kicks-ass.org;tag=533cb9e91f4b999cf76861cbb9ed54ed-
> 4d2a
> CSeq: 10 MESSAGE
> Call-ID: 39dbdbfe-12614 at 127.0.0.1
> Content-Length: 428
> User-Agent: OpenSER (1.3.1-notls (i386/linux))
>
> version="1.0" encoding="ISO-8859-1"
> ?><chowz><preferences><coupon_count>4</coupon_count><breakfast_start>06:00:00</breakfast_start><breakfast_end>10:30:00</breakfast_end><lunch_start>10:30:00</lunch_start><lunch_end>15:00:00</lunch_end><dinner_start>15:00:00</dinner_start><dinner_end>22:00:00</dinner_end><days_breakfast>255</days_breakfast><days_lunch>255</days_lunch><days_dinner>255</days_dinner></preferences></chowz>

New description:

 I'm using SIMPLE to send SIP MESSAGEs back and forth to an Openser SIP
 SERVER.   Pidgin crashes on incoming SIP MESSAGEs.  Backtrace revealed
 little other than the crash appears to come from the use of  strncmp().  I
 suspect it has something to do with the format of the incoming message.
 Tracing the packets with Wireshark shows that Pidgin is responding with
 200 OK, prior to crashing.

 Incoming SIP MESSAGE causing the crash below.
 {{{
 MESSAGE sip:jason at 98.192.39.160:5062;transport=tcp SIP/2.0
 Max-Forwards: 10
 Via: SIP/2.0/TCP 192.168.1.50;branch=z9hG4bKfbe3.90b9e2e5.0
 Via: SIP/2.0/UDP 98.192.39.160:5060;branch=z9hG4bKfbe3.80b9e2e5.0
 To: sip:jason at texas.kicks-ass.org
 From: sip:chowz at texas.kicks-ass.org;tag=533cb9e91f4b999cf76861cbb9ed54ed-
 4d2a
 CSeq: 10 MESSAGE
 Call-ID: 39dbdbfe-12614 at 127.0.0.1
 Content-Length: 428
 User-Agent: OpenSER (1.3.1-notls (i386/linux))

 version="1.0" encoding="ISO-8859-1"
 ?><chowz><preferences><coupon_count>4</coupon_count><breakfast_start>06:00:00</breakfast_start><breakfast_end>10:30:00</breakfast_end><lunch_start>10:30:00</lunch_start><lunch_end>15:00:00</lunch_end><dinner_start>15:00:00</dinner_start><dinner_end>22:00:00</dinner_end><days_breakfast>255</days_breakfast><days_lunch>255</days_lunch><days_dinner>255</days_dinner></preferences></chowz>
 }}}

--

Comment:

 Please follow [wiki:GetABacktrace the instructions] to get a backtrace and
 attach it to this ticket.[[BR]]We need a backtrace with debug symbols.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/7624#comment:1>
Pidgin <http://pidgin.im>
Pidgin