Summary: | ASTERISK-27654: Crash in ast_sip_failover_request in PJSIP | ||||||
Reporter: | Joshua Elson (joshelson) | Labels: | patch pjsip | ||||
Date Opened: | 2018-02-01 17:03:45.000-0600 | Date Closed: | 2018-02-21 17:08:33.000-0600 | ||||
Priority: | Major | Regression? | |||||
Status: | Closed/Complete | Components: | Resources/res_pjsip_session | ||||
Versions: | 15.2.0 | Frequency of Occurrence | |||||
Related Issues: |
| ||||||
Environment: | Attachments: | ( 0) 0001-res_pjsip-Add-a-check-for-NULL-tdata-in-ast_sip_fail.patch ( 1) 0002-pjsip_distributor-Fix-tdata-leak-in-authenticate.patch ( 2) 0003-AST-2018-005-res_pjsip_transport_management-Move-to-.patch ( 3) ast_sip_failover_request_crash.txt | |||||
Description: | Crash observed in 15.2 a handful of times recently... still looking for a way to reproduce, but figured I'd put trace here in case anyone else was seeing. | ||||||
Comments: | By: Asterisk Team (asteriskteam) 2018-02-01 17:03:45.957-0600 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]. By: Joshua Elson (joshelson) 2018-02-01 17:04:02.651-0600 Backtrace attached. By: snuffy (snuffy) 2018-02-02 00:00:50.181-0600 Hello Joshua, I have experienced the issue as well, there is another bug open for this (hidden) I believe they are looking into it By: George Joseph (gjoseph) 2018-02-02 08:32:44.185-0600 Check if res_pjsip_transport_management.so is loaded. By: George Joseph (gjoseph) 2018-02-02 09:06:45.310-0600 I'm marking this as a security issue because I believe it's the same cause as the issue I just linked which is that if a tcp connection goes away while we're sending a response to an invite, we can see the crash. By: George Joseph (gjoseph) 2018-02-08 08:19:11.929-0600 Can you give the attached patches for 15 a shot? |