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 10951 - X Font Server DoS and Buffer Overflow Vulnerabilities
X Font Server DoS and Buffer Overflow Vulnerabilities
Status: CLOSED DUPLICATE of bug 10877
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
: Security
Depends On:
  Show dependency treegraph
Reported: 2000-04-20 18:10 EDT by p.hummel
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-05-08 10:18:31 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-2001:071 high SHIPPED_LIVE : New updated XFree86 packages available 2001-05-24 00:00:00 EDT

  None (edit)
Description p.hummel 2000-04-20 18:10:39 EDT
A denial of service exists in the X11 font server shipped with RedHat
Linux 6.x. Due to improper input validation, it is possible for any user
to crash the X fontserver. This will prevent the X server from functioning

Additional, similar problems exist in the stock xfs. Users can crash the
font server remotely, and potential exists for buffer overruns. The crux
of the problem stems from the font server being lax about verifying
network input. While no exploits exist, it is likely they are available in
private circles, and can result in remote root compromise.

RedHat Linux 6.2 sparc
RedHat Linux 6.2 i386
RedHat Linux 6.2 alpha
RedHat Linux 6.1 sparc
RedHat Linux 6.1 i386
RedHat Linux 6.1 alpha
RedHat Linux 6.0 sparc
RedHat Linux 6.0 i386
RedHat Linux 6.0 alpha
Comment 1 Bernhard Rosenkraenzer 2000-12-20 07:50:50 EST

*** This bug has been marked as a duplicate of 10877 ***

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