Bug 1488033 (CVE-2017-14098, CVE-2017-14099, CVE-2017-14100) - CVE-2017-14098 CVE-2017-14099 CVE-2017-14100 asterisk: Multiple vulnerabilities
Summary: CVE-2017-14098 CVE-2017-14099 CVE-2017-14100 asterisk: Multiple vulnerabilities
Keywords:
Status: CLOSED RAWHIDE
Alias: CVE-2017-14098, CVE-2017-14099, CVE-2017-14100
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1488034 1488035
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-04 07:49 UTC by Andrej Nemec
Modified: 2019-09-29 14:20 UTC (History)
4 users (show)

Fixed In Version: asterisk 13.17.1, asterisk 14.6.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-04 08:38:04 UTC
Embargoed:


Attachments (Terms of Use)

Description Andrej Nemec 2017-09-04 07:49:19 UTC
CVE-2017-14098 - AST-2017-007:

In the pjsip channel driver (res_pjsip) in Asterisk 13.x before 13.17.1 and 14.x before 14.6.1, a carefully crafted tel URI in a From, To, or Contact header could cause Asterisk to crash. 

http://downloads.asterisk.org/pub/security/AST-2017-007.html
https://issues.asterisk.org/jira/browse/ASTERISK-27152

CVE-2017-14099 - AST-2017-005:

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.

http://downloads.asterisk.org/pub/security/AST-2017-005.html
https://issues.asterisk.org/jira/browse/ASTERISK-27013

CVE-2017-14100 - AST-2017-006:

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 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.

http://downloads.asterisk.org/pub/security/AST-2017-006.html
https://issues.asterisk.org/jira/browse/ASTERISK-27103

Comment 1 Andrej Nemec 2017-09-04 07:50:39 UTC
Created asterisk tracking bugs for this issue:

Affects: epel-6 [bug 1488035]
Affects: fedora-all [bug 1488034]

Comment 2 Jared Smith 2017-09-04 08:38:04 UTC
This has been fixed in the 14.6.1 release in Rawhide.


Note You need to log in before you can comment on or make changes to this bug.