Your submission was sent successfully! Close

You have successfully unsubscribed! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates about Ubuntu and upcoming events where you can meet our team.Close

CVE-2017-14099

Published: 2 September 2017

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.

Priority

Low

Cvss 3 Severity Score

7.5

Score breakdown

Status

Package Release Status
asterisk
Launchpad, Ubuntu, Debian
artful Not vulnerable
(1:13.17.1~dfsg-1ubuntu1)
bionic Not vulnerable
(1:13.17.1~dfsg-1ubuntu1)
cosmic Not vulnerable
(1:13.17.1~dfsg-1ubuntu1)
disco Not vulnerable
(1:13.17.1~dfsg-1ubuntu1)
eoan Not vulnerable
(1:13.17.1~dfsg-1ubuntu1)
focal Not vulnerable
(1:13.17.1~dfsg-1ubuntu1)
groovy Not vulnerable
(1:13.17.1~dfsg-1ubuntu1)
hirsute Not vulnerable
(1:13.17.1~dfsg-1ubuntu1)
impish Not vulnerable
(1:13.17.1~dfsg-1ubuntu1)
jammy Not vulnerable
(1:13.17.1~dfsg-1ubuntu1)
kinetic Not vulnerable
(1:13.17.1~dfsg-1ubuntu1)
lunar Not vulnerable
(1:13.17.1~dfsg-1ubuntu1)
mantic Not vulnerable
(1:13.17.1~dfsg-1ubuntu1)
noble Not vulnerable
(1:13.17.1~dfsg-1ubuntu1)
trusty Does not exist
(trusty was needed)
upstream
Released (1:13.17.1~dfsg-1)
xenial Needed

zesty Ignored
(end of life)
Patches:
Introduced by

80b8c2349c427a94a428670f1183bdc693936813

Fixed by cb565f9b59b7879abe3cceb37e8994f00df94a17

Severity score breakdown

Parameter Value
Base score 7.5
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Scope Unchanged
Confidentiality High
Integrity impact None
Availability impact None
Vector CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N