Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 229266

Summary: CVE-2007-1007 gnomemeeting format string flaw
Product: Red Hat Enterprise Linux 4 Reporter: Josh Bressers <bressers>
Component: gnomemeetingAssignee: Monty <cmontgom>
Status: CLOSED ERRATA QA Contact:
Severity: urgent Docs Contact:
Priority: medium    
Version: 4.0CC: kem
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: impact=critical,source=secunia,reported=20070219,public=20070213
Fixed In Version: RHSA-2007-0086 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-02-20 12:06:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Josh Bressers 2007-02-19 20:37:42 UTC
+++ This bug was initially created as a clone of Bug #229259 +++

A format string flaw was found in the way Ekiga processes certain messages form
remote clients.  This flaw could allow a remote attacker to execute arbitrary
code as the user running Ekiga.  This flaw also affects gnomemeeting

This flaw also affects RHEL3

Comment 1 Josh Bressers 2007-02-19 20:44:22 UTC
<mjcox> well a case of replacing   gnomemeeting_log_insert (msg); with  
gnomemeeting_log_insert ("%s",msg); etc

Comment 3 Mark J. Cox 2007-02-20 08:56:09 UTC
I think it's important to note that the format string flaws in Ekiga are not the
same as the format string flaws in Gnomemeeting, although they are of a similar
root cause..  In Ekiga this occurs because the remote name is passed to a
display function as a format string, in GnomeMeeting because the remote name is
passed to a logging function as a format string.  Therefore there are two CVE
names even though the way to trigger these flaws is the same (connect with a
malicious name).

Comment 5 Red Hat Bugzilla 2007-02-20 12:06:15 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.