Bug 203174

Summary:	vncserver PCF handling Integer overflow
Product:	[Fedora] Fedora	Reporter:	Josh Bressers <bressers>
Component:	vnc	Assignee:	Adam Tkac <atkac>
Status:	CLOSED NOTABUG	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5	CC:	ovasik, xgl-maint
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-10-25 09:20:52 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Josh Bressers 2006-08-18 19:27:36 UTC

+++ This bug was initially created as a clone of Bug #203172 +++

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:
https://bugs.freedesktop.org/show_bug.cgi?id=7535

-- Additional comment from bressers on 2006-08-14 14:09 EST --
The upstream patch is attachment 134155 [details]


-- Additional comment from bressers 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

Comment 1 Josh Bressers 2006-08-18 19:28:38 UTC

Scratch that RHEL comment above, but this will need to be fixed in FC6

Comment 2 Marek Grac 2006-08-23 12:17:48 UTC

Affected code is not in the VNC package

Comment 3 Josh Bressers 2006-08-25 18:47:02 UTC

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.

Comment 4 Adam Tkac 2006-10-25 08:55:13 UTC

hmm, this bug is only in versions of vnc to FC-4. FC-5 and up uses different
xserver which is not affected...