Summary: | <net-misc/zaptel-1.2.27-r1 /dev/zap/ctl Memory overwrite (CVE-2008-{5396,5744}) | ||
---|---|---|---|
Product: | Gentoo Security | Reporter: | Robert Buchholz (RETIRED) <rbu> |
Component: | Vulnerabilities | Assignee: | Gentoo Security <security> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | chainsaw, kfm, rajiv, voip+disabled |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://bugs.digium.com/view.php?id=13954 | ||
Whiteboard: | B1 [noglsa] | ||
Package list: | Runtime testing required: | --- |
Description
Robert Buchholz (RETIRED)
![]() According to the upstream but, this also affects 1.2. Patch is upstream. (In reply to comment #1) > According to the upstream but, this also affects 1.2. Patch is upstream. ^^^^^ bug, obviously The upstream patch is incomplete, please see: http://www.openwall.com/lists/oss-security/2008/12/19/2 This is CVE-2008-5744 (which does not affect us if we do not bump using the patch). CVE-2008-5744 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-5744): Array index error in the dahdi/tor2.c driver in Zaptel (aka DAHDI) 1.4.11 and earlier allows local users in the dialout group to overwrite an integer value in kernel memory by writing to /dev/zap/ctl, related to an incorrect tor2 patch for CVE-2008-5396 that uses the wrong variable in a range check against the value of lc->sync. net-misc/zaptel-1.2.27-r1 in cvs. I have confirmed the patch is indeed the fixed one. Apparently the incomplete patch never made it into the SVN. Arches, please test and mark stable: =net-misc/zaptel-1.2.27-r1 Target keywords : "amd64 ppc x86" rbu: the incomplete patch affected only dahdi and not zaptel 1.2*. amd64/x86 stable This fails to compile on ppc due to the kernel module eclass incorrectly determining the architecture (it detects ppc instead of powerpc). Seems like it works with my current kernel. Marked ppc stable. GLSA Request filed. At this point, zaptel is no longer in the portage tree - nor is any version of asterisk that supports it. security team: please close this bug as 'invalid'. zaptel is no longer in the tree. (In reply to comment #14) > security team: please close this bug as 'invalid'. zaptel is no longer in the > tree. Hi, Rajiv. We need to publish a GLSA before we can close this bug. Feel free to email me or the team if you have questions on the policy. Thanks. Removed from tree long time ago |