메뉴 건너뛰기

GREATUSER

cve

CVE-2017-14099

관리자 2017.09.04 03:00 조회 수 : 7

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 symmetric RTP support, this introduced an avenue where media could be hijacked. Instead of only learning a new address when expected, the new code allowed a new source address to be learned at all times. If a flood of RTP traffic was received, the strict RTP support would allow the new address to provide media, and (with symmetric RTP enabled) outgoing traffic would be sent to this new address, allowing the media to be hijacked. Provided the attacker continued to send traffic, they would continue to receive traffic as well.


원문출처 : https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-14099
번호 제목 글쓴이 날짜 조회 수
212 CVE-2017-1693 관리자 2018.01.25 6
211 CVE-2017-7327 관리자 2018.01.25 6
210 CVE-2017-7325 관리자 2018.01.25 6
209 CVE-2017-18044 관리자 2018.01.25 6
208 CVE-2018-5957 관리자 2018.01.25 6
207 CVE-2018-5956 관리자 2018.01.25 6
206 CVE-2016-3234 관리자 2016.06.17 7
205 CVE-2016-6992 관리자 2016.10.14 7
204 CVE-2017-6570 관리자 2017.03.10 7
203 CVE-2017-0005 관리자 2017.03.18 7
202 CVE-2016-10317 관리자 2017.04.04 7
201 CVE-2017-12816 관리자 2017.08.27 7
» CVE-2017-14099 관리자 2017.09.04 7
199 CVE-2017-0898 관리자 2017.09.16 7
198 CVE-2017-2893 관리자 2017.11.09 7
위로