Gentoo: GLSA-201206-05: Asterisk: Multiple vulnerabilities
Summary
Multiple vulnerabilities have been found in Asterisk:
* An error in manager.c allows shell access through the MixMonitor
application, GetVar, or Status (CVE-2012-2414).
* An error in chan_skinny.c could cause a heap-based buffer overflow
(CVE-2012-2415).
* An error in chan_sip.c prevents Asterisk from checking if a channel
exists before connected line updates (CVE-2012-2416).
* An error in chan_iax2.c may cause an invalid pointer to be called
(CVE-2012-2947).
* chan_skinny.c contains a NULL pointer dereference (CVE-2012-2948).
Resolution
All Asterisk users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=net-misc/asterisk-1.8.12.1"
References
[ 1 ] CVE-2012-2414 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-2414 [ 2 ] CVE-2012-2415 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-2415 [ 3 ] CVE-2012-2416 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-2416 [ 4 ] CVE-2012-2947 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-2947 [ 5 ] CVE-2012-2948 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-2948
Availability
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201206-05
Concerns
Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.
Synopsis
Multiple vulnerabilities in Asterisk might allow remote attackers to execute arbitrary code.
Background
Asterisk is an open source telephony engine and toolkit.
Affected Packages
------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 net-misc/asterisk < 1.8.12.1 >= 1.8.12.1
Impact
===== A remote attacker could execute arbitrary code with the privileges of the process or cause a Denial of Service condition.
Workaround
There is no known workaround at this time.