Bug 1525689 (CVE-2017-17664)
| Summary: | CVE-2017-17664 asterisk: Remote DOS via compound RTCP packet | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | Pedro Sampaio <psampaio> |
| Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
| Status: | CLOSED UPSTREAM | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | bennie.joubert, itamar, jsmith.fedora, rbryant, sfowler |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| 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: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-06-08 03:34:13 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1525690, 1525691 | ||
| Bug Blocks: | |||
Created asterisk tracking bugs for this issue: Affects: epel-6 [bug 1525691] Affects: fedora-all [bug 1525690] *** Bug 1525795 has been marked as a duplicate of this bug. *** 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. |
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: https://issues.asterisk.org/jira/browse/ASTERISK-27382 https://issues.asterisk.org/jira/browse/ASTERISK-27429 Upstream patch: http://downloads.asterisk.org/pub/security/AST-2017-012-13.diff http://downloads.asterisk.org/pub/security/AST-2017-012-14.diff