[asterisk-bugs] [Asterisk 0019009]: [patch] Remote bridging of certain IPs causes segfault

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=19009 
====================================================================== 
Reported By:                naomi
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   19009
Category:                   Core/Netsock
Reproducibility:            sometimes
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.8.3.2 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-03-22 07:58 CDT
Last Modified:              2011-03-28 07:54 CDT
====================================================================== 
Summary:                    [patch] Remote bridging of certain IPs causes
segfault
Description: 
When remotely bridging two SIP channels, Asterisk dies with a segfault.

I can reproduce this reliably (on about every second call) with one
particular DDI and one particular outgoing SIP trunk, and never otherwise.


There seems to be a null pointer passed to ast_sockaddr_resolve in
netsock.c when it happens.

I fear this may be a re-emergence of a bug that was mentioned in a Linux
security tracker in 2007:

http://www.linuxsecurity.com/content/view/128447
====================================================================== 

---------------------------------------------------------------------- 
 (0133135) wdoekes (reporter) - 2011-03-28 07:54
 https://issues.asterisk.org/view.php?id=19009#c133135 
---------------------------------------------------------------------- 
Try this patch. It ignores a 200 without Contact if pvt->sa is already set
(has a non-zero port). 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-03-28 07:54 wdoekes        Note Added: 0133135                          
======================================================================