[asterisk-bugs] [JIRA] (ASTERISK-29203) res_pjsip_t38: Crash when changing state

[Asterisk Team (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-29203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Asterisk Team updated ASTERISK-29203:
-------------------------------------

    Target Release Version/s: 17.9.2

> res_pjsip_t38: Crash when changing state
> ----------------------------------------
>
>                 Key: ASTERISK-29203
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29203
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_session, Resources/res_pjsip_t38
>    Affects Versions: 16.13.0, 16.14.0, 16.15.0, 16.16.0
>         Environment: Ubuntu 18.04.5 LTS, kernel 5.3.0, Asterisk 16.16.0.
>            Reporter: Gregory Massel
>            Assignee: Kevin Harwell
>            Severity: Major
>              Labels: fax, patch, security
>      Target Release: 16.16.1, 17.9.2, 18.2.1
>
>         Attachments: AST-2021-002.pdf, ASTERISK-29203.diff, call1.pcap, call2-cpe-leg.pcap, call2.pcap, core-brief.txt-vpbx0-2020-12-08-11h04, core-brief.txt-vpbx1-2020-12-08-15h32, core-brief.txt-vpbx5-2020-12-08-13h51, core-full.txt-vpbx0-2020-12-08-11h04, core-full.txt-vpbx1-2020-12-08-15h32, core-full.txt-vpbx5-2020-12-08-13h51, core-info.txt-vpbx0-2020-12-08-11h04, core-info.txt-vpbx1-2020-12-08-15h32, core-info.txt-vpbx5-2020-12-08-13h51, core-locks.txt-vpbx0-2020-12-08-11h04, core-locks.txt-vpbx1-2020-12-08-15h32, core-locks.txt-vpbx5-2020-12-08-13h51, core-thread1.txt-vpbx0-2020-12-08-11h04, core-thread1.txt-vpbx1-2020-12-08-15h32, core-thread1.txt-vpbx5-2020-12-08-13h51, crashed_asterisk-to-upstream_asterisk_switch.pcap, phone-to-asterisk-via-proxy.pcap, sip_trace_2.png, sip_trace.png, verbose-log
>
>
> Three different systems running Asterisk 16.15.0 have segfaulted today. Coredumps show the exact same issue within t38_change_state.
> The only recent change has been upgrading from 16.12.0 to 16.15.0 (which was done 6 days ago) hence it would appear that this bug was introduced after 16.12.0.



--
This message was sent by Atlassian JIRA
(v6.2#6252)