[reSIProcate] crash after receiving invalid Via line

[Jason Fischl]

Just add in the following check:

if (! (exists(h_Vias) && !empty(h_Vias) ...

Good find!

Jason


On 11/3/06, Justin Matthews <jmatthewsr at gmail.com> wrote:
> The stack is crashing when receiving a request with a via line equal to
> "Via: ".  The actual crash occurs in SipMessage.cxx:435,
> SipMessage::getRFC2543TransactionId, when accessing the via header.  The
> header exists in the mheaders container of the SipMessage, but it does not
> contain any values, so the front() call on line 435 fails.
>
> Can some initial checking be done in the MsgHeaderScanner.cxx,
> processMsgHeaderStatusLine() to drop this message?
>
> Thanks,
>
> -Justin
>
>
>
> Example request:
>
> CANCEL sip:dest at 192.168.2.31 SIP/2.0
> Via:
> From: "12345" <sip:12345 at 192.168.2.11>
> To: <sip:dest at 192.168.2.31>
> Call-ID: D71644F5-560F-44BE-AB36-F5FF7790A349 at 192.168.2.11
> Date: Fri, 03 Nov 2006 23:01:23 GMT
> CSeq: 0 CANCEL
> Contact: <sip:12345 at 192.168.2.11:5060>
> Content-Length: 0
>
>
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>