CVE-2018-7285

N/A
Published: February 22, 2018 at 12:00 AM UTC
Updated: June 17, 2026 at 02:02 AM UTC
1 product affected across 1 vendorAsterisk

Using N/A by N/A?

Get instant alerts when new vulnerabilities affect N/A - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 5%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

15.0.0 ≤ v ≤ 15.2.1

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (3)

VDB Entryx_refsource_BIDThird Party Advisory
http://www.securityfocus.com/bid/103149
VDB Entryx_refsource_SECTRACKThird Party Advisory
http://www.securitytracker.com/id/1040415

CVSS

Confidentiality
NONE
Integrity
NONE
Availability
PARTIAL
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card