ASA-2007-010: Two stack buffer overflows in SIP channel's T.38 SDP parsing code http://lists.grok.org.uk/pipermail/full-disclosure/2007-April/053969.html ASA-2007-011: Multiple problems in SIP channel parser handling response codes http://lists.grok.org.uk/pipermail/full-disclosure/2007-April/053967.html ASA-2007-012: Remote Crash Vulnerability in Manager Interface http://lists.grok.org.uk/pipermail/full-disclosure/2007-April/053968.html
ASA-2007-010 doesn't apply since we don't have 1.4.x in portage and previous versions aren't affected.
ASA-2007-011 was fixed in gentoo bug 171467.
asterisk-1.2.17 contains fixes for ASA-2007-011 and ASA-2007-012. it does not contain fixes for ael (bug #171884) however - even asterisk 1.2.18 lacks fixes for this.
Arches please test and mark stable. Target keywords are: asterisk-1.2.17.ebuild:KEYWORDS="~alpha ~amd64 ~hppa ~ppc sparc x86"
sparc stable.
x86 stable
This one is ready for GLSA decision. I vote YES.
I'm voting no. marginal software - specific configuration (C3) and a specific action to cause a DoS.
I fail to see the specific configuration for ASA-2007-011, am I just overlooking something?
I vote yes - it may be marginal, but for people who are using it, this is very critical software (911 calls, etc), and the SIP DoS could be a huge problem.
2 YES votes and 1 NO vote. Lets have a GLSA. voip we forgot 1.x, should that be bumped or will the comment on GLSA 200704-01 suffice?
Seems like aetius and I overlooked comment #2. Agreeing with Daniel then and reverting to a full NO and closing. Feel free to reopen if you disagree.
asterisk 1.0.12 (and our -r2) is vulnerable to ASA-2007-012 but the risk is minimal. the manager interface is typically not exposed outside trusted networks, and not enabled by default. i will patch in our cvs. no glsa required.
Rajiv please comment here once it is done and I will call arches.
asterisk 1.0.12 is now package masked and will not be patched. closing.