Bug 231684 (CVE-2007-1667) - CVE-2007-1667 XGetPixel() integer overflow
Summary: CVE-2007-1667 XGetPixel() integer overflow
Alias: CVE-2007-1667
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2007-03-09 22:36 UTC by Josh Bressers
Modified: 2019-09-29 12:20 UTC (History)
3 users (show)

Fixed In Version: RHSA-2007-0125
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-04-03 19:15:18 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2007:0125 0 normal SHIPPED_LIVE Important: XFree86 security update 2007-04-03 19:15:10 UTC

Description Josh Bressers 2007-03-09 22:36:55 UTC
A bug recently showed up in the Debian BTS that describes an integer overflow in
X's XGetPixel() function


The report incorrectly states it is a buffer overflow.  The bug also has a
proposed patch and reproducer for this flaw.

The issue is that the XInitImage() function allows the caller to supply silly
values, which can cause several integer overflow.  A call to XGetPixel() can
also result in integer overflows.  While one would expect the calling
application to sanitize the data passed to XInitImage(), the library should also
be smart enough to prevent the caller from giving it bad data.

Comment 1 Josh Bressers 2007-03-09 22:38:48 UTC
This flaw should also affect RHEL2.1

Comment 2 Matěj Cepl 2007-03-12 23:35:39 UTC
Patches from the Debian bug were attached to the RHEL 5 clone of this bug -- bug

Comment 5 Red Hat Bugzilla 2007-04-03 19:15:18 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.


Note You need to log in before you can comment on or make changes to this bug.