[asterisk-bugs] [JIRA] (ASTERISK-26927) pjproject_bundled: Crash on pj_ssl_get_info() while ioqueue_on_read_complete().

[Alexander Traud (JIRA)]

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

Alexander Traud updated ASTERISK-26927:
---------------------------------------

    Comment: was deleted

(was: 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].)

> pjproject_bundled: Crash on pj_ssl_get_info() while ioqueue_on_read_complete().
> -------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26927
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26927
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip/Bundling
>    Affects Versions: 13.14.1, 14.3.1, GIT
>            Reporter: Alexander Traud
>            Severity: Critical
>         Attachments: 0048-r5576-svn-backport-tls-crash.patch
>
>
> When the Asterisk channel driver {{res_pjsip}} offers SIP-over-TLS, sometimes, not reproducible, Asterisk crashes in {{pj_ssl_sock_get_info()}} because a NULL pointer was read. The attached patch avoids this crash.
> From my point of view, this is a security issue because an outside, unauthenticated attacker might be able to tear down your Asterisk. However although explained to the PJProject team, they made the fix (and therefore the issue) public already. Consequently, it does not make any sense not to disclose it within Asterisk. Finally, I do not know hot to trigger this issue on purpose. I faced this issue three times within four months.



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