Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 166856 - CAN-2005-2495 multiple integer overflows
CAN-2005-2495 multiple integer overflows
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: xorg-x11 (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Søren Sandmann Pedersen
: Security
Depends On:
  Show dependency treegraph
Reported: 2005-08-26 10:49 EDT by Josh Bressers
Modified: 2014-06-18 05:07 EDT (History)
3 users (show)

See Also:
Fixed In Version: RHSA-2005-396
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-13 13:06:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:396 moderate SHIPPED_LIVE Important: xorg-x11 security update 2005-09-13 00:00:00 EDT

  None (edit)
Description Josh Bressers 2005-08-26 10:49:19 EDT

What is going on here is that an X client is trying to allocate a pixmap
of size 9GB. Because of
an integer overflow this is not caught and instead a pixmap of size 1GB
is allocated. When the
client then tries to access the pixmap we get a server crash.

This seems exploitable to me: a client could allocate a pixmap of size
4GB + 4byte, causing
the server to allocate just 4 bytes. Then the client could use
XDrawPoint() and XGetImage() to
read and write any location in the X server address space. It could
first use XGetImage to search
for the stack, then use XDrawPoint to rewrite it to return into another
pixmap the client allocated,
thus getting the X server to execute arbitrary code.

This issue was discovered by Luke Hutchison, with the security implications and
patch found by Soeren Sandmann.
Comment 1 Josh Bressers 2005-09-13 12:35:07 EDT
Lifting embargo
Comment 2 Red Hat Bugzilla 2005-09-13 13:06:31 EDT
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.