First published: Thu Feb 22 2018(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Digium Asterisk | >=15.0.0<=15.2.1 | |
debian/asterisk | 1:16.2.1~dfsg-1+deb10u2 1:16.28.0~dfsg-0+deb10u3 1:16.28.0~dfsg-0+deb11u3 1:20.4.0~dfsg+~cs6.13.40431414-2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this issue is CVE-2018-7285.
CVE-2018-7285 has a severity rating of 7.5 (high).
Asterisk versions 15.x through 15.2.1 and Digium Asterisk are affected by CVE-2018-7285.
To mitigate CVE-2018-7285, update to the following versions: Asterisk 15.x through 15.2.1 should be updated to version 1:16.2.1~dfsg-1+deb10u2 or later, Digium Asterisk should be updated to a version later than 15.2.1.
More information about CVE-2018-7285 can be found at the following references: [AST-2018-001](http://downloads.asterisk.org/pub/security/AST-2018-001.html), [SecurityFocus](http://www.securityfocus.com/bid/103149), [SecurityTracker](http://www.securitytracker.com/id/1040415).