CVE Catalog

CVE-2017-14099

High
Published: Translated: NVD NIST

Summary

In Asterisk 11.x before 11.25.2, 13.x before 13.17.1, and 14.x before 14.6.1, there is a vulnerability that allows unauthorized data disclosure, potentially leading to media takeover in the RTP stack. This issue relates to the 'strictrtp' option, which is enabled by default and can be exploited by an attacker with careful timing.

Risk Assessment

Organizations may be exposed to unauthorized access to media data, which could lead to serious breaches of privacy and communication security.

Recommendation

It is recommended to update Asterisk to the latest version to mitigate this vulnerability and consider enabling the 'strictrtp' option to enhance security.

Related vulnerabilities

Original NVD description (English source)

In res/res_rtp_asterisk.c in Asterisk 11.x before 11.25.2, 13.x before 13.17.1, and 14.x before 14.6.1 and Certified Asterisk 11.x before 11.6-cert17 and 13.x before 13.13-cert5, unauthorized data disclosure (media takeover in the RTP stack) is possible with careful timing by an attacker. The "strictrtp" option in rtp.conf enables a feature of the RTP stack that learns the source address of media for a session and drops any packets that do not originate from the expected address. This option is enabled by default in Asterisk 11 and above. The "nat" and "rtp_symmetric" options (for chan_sip and chan_pjsip, respectively) enable symmetric RTP support in the RTP stack. This uses the source address of incoming media as the target address of any sent media. This option is not enabled by default, but is commonly enabled to handle devices behind NAT. A change was made to the strict RTP support in the RTP stack to better tolerate late media when a reinvite occurs. When combined with the symmetr

Vulnerability data from NVD (NIST) · CISA KEV · EPSS