Bug 1166683 (CVE-2014-8414) - CVE-2014-8414 asterisk: High call load may result in hung channels in ConfBridge [AST-2014-014]
Summary: CVE-2014-8414 asterisk: High call load may result in hung channels in ConfBri...
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2014-8414
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1166684
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-21 13:17 UTC by Martin Prpič
Modified: 2019-09-29 13:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-08 02:36:31 UTC
Embargoed:


Attachments (Terms of Use)

Description Martin Prpič 2014-11-21 13:17:22 UTC
The following issue was made public in the AST-2014-014 advisory [1][2]:

The ConfBridge application uses an internal bridging API to implement
conference bridges. This internal API uses a state model for channels
within the conference bridge and transitions between states as different
things occur. Under load it is possible for some state transitions to be
delayed causing the channel to transition from being hung up to waiting for
media. As the channel has been hung up remotely no further media will
arrive and the channel will stay within ConfBridge indefinitely.

Patches for this issue are linked to in the AST-2014-014 [1][2] advisory.

References:
[1] http://downloads.asterisk.org/pub/security/AST-2014-014.pdf
[2] http://seclists.org/fulldisclosure/2014/Nov/67

Comment 1 Martin Prpič 2014-11-21 13:18:27 UTC
Created asterisk tracking bugs for this issue:

Affects: fedora-all [bug 1166684]

Comment 2 Murray McAllister 2014-11-26 03:53:08 UTC
This issue is assigned CVE-2014-8414:

http://downloads.asterisk.org/pub/security/AST-2014-014.html

Comment 3 Product Security DevOps Team 2019-06-08 02:36:31 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


Note You need to log in before you can comment on or make changes to this bug.