Bug 231070

Summary: CVE-2007-1217 Overflow in CAPI subsystem
Product: Red Hat Enterprise Linux 2.1 Reporter: Marcel Holtmann <holtmann>
Component: kernelAssignee: Don Howard <dhoward>
Status: CLOSED ERRATA QA Contact: Martin Jenner <mjenner>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.1CC: anton, jlieskov, security-response-team
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard: impact=moderate,source=vendorsec,reported=20070213,public=20070126
Fixed In Version: RHSA-2007-0672 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-08-08 18:16:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
BZ 230563 RHEL 2.1AS patch, only compilation tested, need to test with real hardware
none
CVS repository patch, adds CONFIG_CAPI_TRACE option none

Description Marcel Holtmann 2007-03-05 22:17:46 UTC 
The bufprint routine used by capi_cmsg2str does an unbounded vsprintf into a
8192 byte buffer, perhaps hoping it's big enough.

If the content of that vsprintf can be controlled by remote peers, this may lead
to a remote security hole for daemons using CAPI (pppd-capi-plugin,
asterisk-chan-capi, capi4hylafax, ...). Or a DoS.

If the content of that vsprintf can be controlled by local users making use of a
system service (such as sending a fax, making a phone call, ...) that uses CAPI,
this is a privilege escalation or remote authenticated user security hole, or a DoS.
Comment 3 Radovan Augustin 2007-04-06 10:56:33 UTC 
Created attachment 151860 [details]
BZ 230563 RHEL 2.1AS patch, only compilation tested, need to test with real hardware
Comment 4 Radovan Augustin 2007-04-06 10:58:10 UTC 
Created attachment 151862 [details]
CVS repository patch, adds CONFIG_CAPI_TRACE option
Comment 6 Radovan Augustin 2007-05-21 09:29:48 UTC 
Hi,

if it is possible, i would like not to post it, because i can not guarantee that
code is working. All code in patches is not tested. For example, when user will
use patched module, it can cause kernel panic so it is better not to include it?
Plesae correct me if i am wrong.
Comment 10 Red Hat Bugzilla 2007-08-08 18:16:43 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2007-0672.html
Comment 11 Jan Lieskovsky 2007-11-29 14:06:54 UTC 
*** Bug 402751 has been marked as a duplicate of this bug. ***