[asterisk-bugs] [JIRA] (ASTERISK-27262) Leaking eventfd's when using ARI

Asterisk Team (JIRA) noreply at issues.asterisk.org
Fri Sep 8 07:07:08 CDT 2017


    [ https://issues.asterisk.org/jira/browse/ASTERISK-27262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=238586#comment-238586 ] 

Asterisk Team commented on ASTERISK-27262:
------------------------------------------

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].

> Leaking eventfd's when using ARI
> --------------------------------
>
>                 Key: ASTERISK-27262
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27262
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Third-Party/pjproject
>    Affects Versions: 14.6.1
>         Environment: Ubuntu 17.04
>            Reporter: Thomas Wirum Larsen
>
> When using ARI4Java bindings and their Dial() method, Asterisk leaks (fails to close?) an eventfd, leading to a crash once the underlying OS' ulimit is reached.
> This behavior is only seen using dial(). When using originate(), asterisk behaves correctly.
> This bug is reproducible on Asterisk 13x and 14x using Ari4Java 0.4.3 and 0.4.4 and ARI protocol version 1.7 through 1.10. We have been unsuccessful in testing 2.0.0 or 3.0.0 protocol variants, thus we cannot guarantee this behavior exists in the 2x and 3x protocol branches.
> While the actual bug may be in Ari4Java, it is arguable that a REST interface should not be allowed to cause the host to leak file descriptors as this a potential DOS attack (or worse). This is thus clearly a bug in Asterisks implementation of ARI and requires immediate attention.
> We have filed an issue with Ari4Java as well.



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



More information about the asterisk-bugs mailing list