[asterisk-bugs] [Asterisk 0017590]: Crash when freeing buffer in update_curl

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17590 
====================================================================== 
Reported By:                atis
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   17590
Category:                   Resources/res_config_curl
Reproducibility:            have not tried
Severity:                   crash
Priority:                   normal
Status:                     acknowledged
Target Version:             1.6.2.12
Asterisk Version:           SVN 
JIRA:                       SWP-1822 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-07-06 08:54 CDT
Last Modified:              2010-07-29 11:31 CDT
====================================================================== 
Summary:                    Crash when freeing buffer in update_curl
Description: 
free(buffer) causes crash with signal 6 Aborted.

HTTP message is clearly wrong, as it contains PHP error, but this
shouldn't crash asterisk.

        bufsize = 100
        buffer = 0x937c060 "1<br />\n<b>Fatal error</b>:  Call to
undefined function ast_sip_prune_rt() in <b>/opt/voip/web/curl_"
        __PRETTY_FUNCTION__ = "update_curl"

====================================================================== 

---------------------------------------------------------------------- 
 (0125270) tilghman (administrator) - 2010-07-29 11:31
 https://issues.asterisk.org/view.php?id=17590#c125270 
---------------------------------------------------------------------- 
Okay, WHAT are you returning to the update command that you're exceeding
the 100 byte buffer?  You're only supposed to return an integer of how many
rows were affected.  That's 12 bytes long, maximum, and it's unlikely you
should ever return more than 2 bytes. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-07-29 11:31 tilghman       Note Added: 0125270                          
======================================================================