An out-of stack-based buffer write flaw was found in the way the Miliwatt application of the Asterisk, open source telephony toolkit, performed generation of constant audio tone at 1000Hz (the 'o' option) from certain, provided audio packets, when the 'internal_timing' Asterisk configuration file option was disabled. In this configuration, a remote attacker could provide a specially-crafted audio packet file, which once processed by the Miliwatt application would lead to that application crash, or, potentially arbitrary code execution with the privileges of the user running the application. Upstream security advisory: [1] http://downloads.asterisk.org/pub/security/AST-2012-002.pdf Asterisk v1.8.10.1 announcement: [2] http://www.asterisk.org/node/51797 Upstream patch against the v1.8 branch: [3] http://downloads.asterisk.org/pub/security/AST-2012-002-1.8.diff
This issue affects the versions of the asterisk package, as shipped with Fedora release of 15 and 16. Please schedule an update.
Created asterisk tracking bugs for this issue Affects: fedora-all [bug 804045]
CVE request: [4] http://www.openwall.com/lists/oss-security/2012/03/16/10
Added CVE as per http://www.openwall.com/lists/oss-security/2012/03/16/17
asterisk-1.8.10.1-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
asterisk-1.8.10.1-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
asterisk-10.2.1-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
asterisk-1.8.11.1-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
asterisk-10.3.1-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
asterisk-1.8.11.1-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.