[asterisk-bugs] [JIRA] (ASTERISK-21806) Segfault in CHAN_SIP - in _int_malloc while in __ast_cc_config_params_init

[Christopher (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-21806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207272#comment-207272 ] 

Christopher commented on ASTERISK-21806:
----------------------------------------

This looks to be more and more like an IP conflict issue..  a crash had occured on 05/29..  the IP fault was found and corrected...  on 06/04  a laptop was plugged in that had a VM running the same IP as the asterisk server in question..  now mind you this IP was not on the same network segment..  but could be gotten to by routing....  the asterisk server in question here crashed with the same malloc segfault....  it ran fine until 6/08  when a power failure occured and knocked it down... and has been running fine now since 06/08..   it seems doing an arping on it will bring up ANY interface with the IP in arping regardless of the network segment..  the "perceived " IP conflicting machine was another asterisk box with 192.168.10.5 as its eth1. which was UNPLUGGED!.. yet Arping found it through the ETH0 segment. as both this and the conflicting boxes have IP's on their eth0 (not the same IP but same subnet)...  This is a bit scary though as I dont believe asterisk should Crash because of an IP conflict.. seems a security issue if all a hacker has to do to crash a PBX is find its IP and mimick it...

                
> Segfault in CHAN_SIP - in _int_malloc while in __ast_cc_config_params_init
> --------------------------------------------------------------------------
>
>                 Key: ASTERISK-21806
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21806
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 1.8.15.0
>         Environment: CPU: Atom D525, RAM 4GB, Fedora Linux, Kernel 2.6.43.8-1.i686
> 2 Aastra endpoints, 1 Polycom IP-650, 1 96 port SIP to analog gateway
> Asterisk 1.8.15-cert2
>            Reporter: Christopher
>            Assignee: Christopher
>         Attachments: core-dump-maxx-052213.txt, valgrind-052213-1530.txt, valgrind-0523-1545-no-malloc.txt, valgrind-good-052213-1930.txt
>
>
> Segfault occurs whether system is idle or is in-use. it will crash within a day or two even if 0 calls are made on it.  running under safe_asterisk, results in multiple crashes within a few minutes until eventually system ends up in a MUTEX lock. over 3 gigs of RAM available and plenty of disk space at time of first crash. Possibly related to the 96 port gateway producing 96 SIP registrations all at once?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira