Bug 1525689 (CVE-2017-17664) - CVE-2017-17664 asterisk: Remote DOS via compound RTCP packet
Summary: CVE-2017-17664 asterisk: Remote DOS via compound RTCP packet
Alias: CVE-2017-17664
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
: 1525795 (view as bug list)
Depends On: 1525690 1525691
TreeView+ depends on / blocked
Reported: 2017-12-13 21:08 UTC by Pedro Sampaio
Modified: 2019-09-29 14:28 UTC (History)
5 users (show)

Fixed In Version: asterisk 13.18.4, asterisk 14.7.4, asterisk 15.1.4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-06-08 03:34:13 UTC

Attachments (Terms of Use)

Description Pedro Sampaio 2017-12-13 21:08:56 UTC
If a compound RTCP packet is received containing more than one report (for example a Receiver Report and a Sender Report) the RTCP stack will directly store report information outside of allocated memory potentially causing a crash.                                                     
For all versions of Asterisk this vulnerability requires an active call to be established.                               
For versions of Asterisk 13.17.2, 14.6.2, 15.0.0, 13.13-cert6 and greater an additional level of security is placed upon RTCP packets. If the probation period for incoming RTP traffic has passed any received RTCP packets must contain the same SSRC as the RTP traffic. If the RTCP packets do not then they are dropped. This ensures other parties can not inject RTCP packets without they themselves establishing an active call.

Upstream issue:


Upstream patch:


Comment 1 Pedro Sampaio 2017-12-13 21:09:20 UTC
Created asterisk tracking bugs for this issue:

Affects: epel-6 [bug 1525691]
Affects: fedora-all [bug 1525690]

Comment 2 Pedro Sampaio 2017-12-18 20:42:42 UTC
*** Bug 1525795 has been marked as a duplicate of this bug. ***

Comment 3 Product Security DevOps Team 2019-06-08 03:34:13 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.