Red Hat Bugzilla – Bug 203172
vncserver PCF handling Integer overflow
Last modified: 2013-04-30 19:34:01 EDT
+++ This bug was initially created as a clone of Bug #202469 +++
An integer overflow was discovered in the way freetype processes malformed PCF
files. It seems that Xorg also contains the same PCF processing code as
freetype, there it too is vulnerable this issue.
We initally described this issue for freetype in bug 190593.
The upstream bug is here:
-- Additional comment from firstname.lastname@example.org on 2006-08-14 14:09 EST --
The upstream patch is attachment 134155 [details]
-- Additional comment from email@example.com on 2006-08-15 20:42 EST --
Created an attachment (id=134276)
Demo font file
This issue also affects the vncserver shipped with RHEL2.1 and RHEL3
Affected code is not in the VNC package
I can make the vnc server crash by using the demo font file.
Differnt issue perhaps?
My fault, there were two files with same name and I have checked just one of
them. After applying proposed patch the vncserver works correctly (xfontsel
I've done some thinking about this and I'm removing the Security keyword. There
is no way this can be considered a security issue, it's simply a bug.
The only way this is exploitable is if a bad font can be included in the
vncserver font path. That means that an attacker already has access to the
account in question.
Created attachment 158511 [details]
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
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 therefore 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.