Bug 1548090 (CVE-2018-7285) - CVE-2018-7285 asterisk: NULL Pointer Dereference in RTP
Summary: CVE-2018-7285 asterisk: NULL Pointer Dereference in RTP
Alias: CVE-2018-7285
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1548091 1548092
TreeView+ depends on / blocked
Reported: 2018-02-22 16:53 UTC by Laura Pardo
Modified: 2019-09-29 14:33 UTC (History)
4 users (show)

Fixed In Version: asterisk 15.2.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-06-08 03:40:53 UTC

Attachments (Terms of Use)

Description Laura Pardo 2018-02-22 16:53:27 UTC
A NULL pointer access issue was discovered in Asterisk 15.x through 15.2.1. The RTP support in Asterisk maintains its own registry of dynamic codecs and desired payload numbers. While an SDP negotiation may result in a codec using a different payload number, these desired ones are still stored internally. When an RTP packet was received, this registry would be consulted if the payload number was not found in the negotiated SDP. This registry was incorrectly consulted for all packets, even those which are dynamic. If the payload number resulted in a codec of a different type than the RTP stream (for example, the payload number resulted in a video codec but the stream carried audio), a crash could occur if no stream of that type had been negotiated. This was due to the code incorrectly assuming that a stream of that type would always exist.



Comment 1 Laura Pardo 2018-02-22 16:53:50 UTC
Created asterisk tracking bugs for this issue:

Affects: epel-6 [bug 1548092]
Affects: fedora-all [bug 1548091]

Comment 2 Product Security DevOps Team 2019-06-08 03:40:53 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.