Bug 45365 - asterisk: Multiple issues (4.2)
asterisk: Multiple issues (4.2)
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: Security updates
UCS 4.2
Other Linux
: P3 normal (vote)
: UCS 4.2-2-errata
Assigned To: Arvid Requate
Felix Botner
:
Depends on:
Blocks: 40975
  Show dependency treegraph
 
Reported: 2017-09-08 15:28 CEST by Arvid Requate
Modified: 2017-11-08 14:59 CET (History)
0 users

See Also:
What kind of report is it?: Security Issue
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Ticket number:
Bug group (optional): Security
Max CVSS v3 score: 9.8 (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
requate: Patch_Available+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2017-09-08 15:28:43 CEST
Upstream Debian package version 1:11.13.1~dfsg-2+deb8u3 fixes:

* In res/res_rtp_asterisk.c 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. (CVE-2017-14099)

* unauthorized command execution is possible. The app_minivm module has an "externnotify" program configuration option that is executed by the MinivmNotify dialplan application. The application uses the caller-id name and number as part of a built string passed to the OS shell for interpretation and execution. Since the caller-id name and number can come from an untrusted source, a crafted caller-id name or number allows an arbitrary shell command injection. (CVE-2017-14100)
Comment 1 Arvid Requate univentionstaff 2017-10-30 18:18:12 CET
1:11.13.1~dfsg-2+deb8u4 fixes:

* insufficient RTCP packet validation could allow reading stale buffer contents and when combined with the "nat" and "symmetric_rtp" options allow redirecting where Asterisk sends the next RTCP report (CVE-2017-14603)
Comment 2 Arvid Requate univentionstaff 2017-10-30 19:06:51 CET
Package imported from jessie.

Advisory: asterisk.yaml
Comment 3 Felix Botner univentionstaff 2017-11-01 17:34:35 CET
OK - installation
OK - cve's
OK - YAML
Comment 4 Arvid Requate univentionstaff 2017-11-08 14:59:11 CET
<http://errata.software-univention.de/ucs/4.2/210.html>