[Home]

Summary:ASTERISK-28426: Address out of bounds in ast_str_hash
Reporter:Ross Beer (rossbeer)Labels:pjsip
Date Opened:2019-05-23 08:40:39Date Closed:2019-06-08 12:00:03
Priority:MajorRegression?
Status:Closed/CompleteComponents:Resources/res_pjsip
Versions:13.26.0 GIT Frequency of
Occurrence		Occasional
Related
Issues:
Environment:CentOS 7Attachments:( 0) core-asterisk-113633-1558612929-thread1.txt
Description:Asterisk segfaults with 'address out of bounds' when in ast_str_hash:

{noformat}
Thread 1 (Thread 0x7f5f3ca28700 (LWP 113932)):
#0  0x00007f605572d4ac in ast_str_hash (str=0x7f5ec234d248 <Address 0x7f5ec234d248 out of bounds>) at /usr/src/asterisk/asterisk-13-trunk/include/asterisk/strings.h:1202
       hash = 5381
#1  0x00007f605572d512 in transport_monitor_hash_fn (obj=0x7f5ec234d248, flags=64) at res_pjsip/pjsip_transport_events.c:69
       object = 0x7f5ec234d248
       key = 0x7f5ec234d248 <Address 0x7f5ec234d248 out of bounds>
#2  0x000000000045df8e in hash_ao2_find_first (self=0x2e673a8, flags=80, arg=0x7f5ec234d248, state=0x7f5f3ca276a0) at astobj2_hash.c:390
       node = 0x2e673a8
       bucket_cur = 32607
       cmp = 1017280128
#3  0x000000000045c491 in internal_ao2_traverse (self=0x2e673a8, flags=80, cb_fn=0x7f605572d514 <transport_monitor_cmp_fn>, arg=0x7f5ec234d248, data=0x0, type=AO2_CALLBACK_DEFAULT, tag=0x0, file=0x0, line=0, func=0x0) at astobj2_container.c:344
       ret = 0x0
       cb_default = 0x7f605572d514 <transport_monitor_cmp_fn>
       cb_withdata = 0x0
       node = 0x7f5f3ca277e0
       traversal_state = 0x7f5f3ca276a0
       orig_lock = AO2_LOCK_REQ_MUTEX
       multi_container = 0x0
       multi_iterator = 0x0
       __PRETTY_FUNCTION__ = "internal_ao2_traverse"
{noformat}
Comments:By: Asterisk Team (asteriskteam) 2019-05-23 08:40:40.158-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.
By: Benjamin Keith Ford (bford) 2019-05-24 13:54:44.371-0500

Yep, looks like something is going on. Are you running a vanilla 13.26? Do you happen to know what's triggering it, based on what activity is going on in the system at the time?
By: Asterisk Team (asteriskteam) 2019-06-08 12:00:02.225-0500

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines