Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 145513 - x11-base/xorg-x11 Integer overflow in CID parser (CVE-2006-37{39|40})
Summary: x11-base/xorg-x11 Integer overflow in CID parser (CVE-2006-37{39|40})
Alias: None
Product: Gentoo Security
Classification: Unclassified
Component: Vulnerabilities (show other bugs)
Hardware: All Linux
: High critical (vote)
Assignee: Gentoo Security
Whiteboard: A1 [glsa] frilled
Depends on:
Reported: 2006-08-29 12:20 UTC by Sune Kloppenborg Jeppesen (RETIRED)
Modified: 2007-05-31 10:56 UTC (History)
7 users (show)

See Also:
Package list:
Runtime testing required: ---

libXfont.diff (libXfont.diff,2.17 KB, patch)
2006-08-29 12:22 UTC, Sune Kloppenborg Jeppesen (RETIRED)
no flags Details | Diff
libXfont-1.2.0-r2.ebuild (libXfont-1.2.0-r2.ebuild,999 bytes, text/plain)
2006-09-05 10:19 UTC, Donnie Berkholz (RETIRED)
no flags Details
libXfont-1.2.0-r2.ebuild (libXfont-1.2.0-r2.ebuild,983 bytes, text/plain)
2006-09-05 10:21 UTC, Donnie Berkholz (RETIRED)
no flags Details
1.2.0-cid-overflows.patch (1.2.0-cid-overflows.patch,2.77 KB, patch)
2006-09-07 00:08 UTC, Donnie Berkholz (RETIRED)
no flags Details | Diff
1.2.0-cid-overflows.patch-6447.out (1.2.0-cid-overflows.patch-6447.out,3.17 KB, text/plain)
2006-09-07 04:00 UTC, Thomas Cort (RETIRED)
no flags Details
1.2.0-cid-overflows.patch (1.2.0-cid-overflows.patch,2.18 KB, patch)
2006-09-07 09:37 UTC, Donnie Berkholz (RETIRED)
no flags Details | Diff
1.2.0-cid-overflows.patch (1.2.0-cid-overflows.patch,2.26 KB, patch)
2006-09-07 10:31 UTC, Thomas Cort (RETIRED)
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Sune Kloppenborg Jeppesen (RETIRED) gentoo-dev 2006-08-29 12:20:39 UTC
iDefense has contacted xorg_security about multiple vunlerabilites they 
found in X's CID fonts parser. These vulnerabilites, based on integer 
overflows, are exploitable by a user able to connect to the X server to 
execute code with the X server's privileges.

The affected code has not changed since XFree86 3.3.6. So all versions 
of X using the Type1 code are affected.

In X versions after XFree86 4.4 (may be already 4.3, I'm not sure) is to 
only use the "freetype" module to handle Type 1 fonts. This module 
doesn't use the vulnerable code to parse Type 1 fonts.
Comment 1 Sune Kloppenborg Jeppesen (RETIRED) gentoo-dev 2006-08-29 12:22:15 UTC
Created attachment 95407 [details, diff]
Comment 2 Wolf Giesen (RETIRED) gentoo-dev 2006-09-05 07:06:45 UTC
x11 team, please advise - I have some problems understanding this one ( is supposed to be vulnerable because it was forked at 4.3 and thus contains the affected code?). Is there anything in queue upstream?
Comment 3 Wolf Giesen (RETIRED) gentoo-dev 2006-09-05 07:12:19 UTC
Forgot to assign, sorry.
Comment 4 Wolf Giesen (RETIRED) gentoo-dev 2006-09-05 07:25:29 UTC
Donnie, I'm not sure you're the right one to CC (since x11 can't read restricted yet), but maybe you can help us here (or point me to somebody else)? Thanks!
Comment 5 Donnie Berkholz (RETIRED) gentoo-dev 2006-09-05 10:04:18 UTC
Cool, another libXfont vuln (bug #144092 remains open waiting for advisory). Upstream bugs are and (both are security-restricted so you can't access them).

All X versions should be vulnerable. The point at the end of comment #0 is that only CID fonts will cause the problem because they still use the Type1/ code, but typical Type 1 fonts use the FreeType parser.
Comment 6 Wolf Giesen (RETIRED) gentoo-dev 2006-09-05 10:11:50 UTC
Ok, thank you. So we wait for upstream. Do you have the exact embargo time, Donnie?
Comment 7 Donnie Berkholz (RETIRED) gentoo-dev 2006-09-05 10:14:17 UTC
Latest info on the bugs indicates no date set yet, but I'm not privy to discussions on the security mail alias.
Comment 8 Donnie Berkholz (RETIRED) gentoo-dev 2006-09-05 10:19:41 UTC
Created attachment 96088 [details]

Here's an ebuild to test. Rename libXfont.diff to 1.2.0-cid-overflows.patch and drop it in files/.
Comment 9 Donnie Berkholz (RETIRED) gentoo-dev 2006-09-05 10:21:45 UTC
Created attachment 96089 [details]

Woops, that one was broken. Try this instead
Comment 10 Wolf Giesen (RETIRED) gentoo-dev 2006-09-05 13:42:00 UTC
I think I can try in the morning ... x86 only, I'm afraid, since my Alphas lag waay behind :P

An exploit to check would be nice, though :)
Comment 11 Wolf Giesen (RETIRED) gentoo-dev 2006-09-06 23:42:42 UTC
Since we seem to have all we need, humbly asking sec liaisons to test and report.
Comment 12 Markus Rothe (RETIRED) gentoo-dev 2006-09-06 23:57:10 UTC
looks good on ppc64. it's ok to have this marked stable on ppc64 while commiting to the tree.
Comment 13 Wolf Giesen (RETIRED) gentoo-dev 2006-09-07 00:00:45 UTC
Corsair, please don't commit yet, this is a prestabling request; thanks!
Comment 14 Donnie Berkholz (RETIRED) gentoo-dev 2006-09-07 00:08:49 UTC
Created attachment 96254 [details, diff]

Updated patch, changes includes around a bit. Reportedly fixes a compilation issue in module subdir.
Comment 15 Markus Rothe (RETIRED) gentoo-dev 2006-09-07 00:11:32 UTC
What I meant was: When you commit then it would be ok for me to commit this streight to stable on ppc64 ^^
Comment 16 Thomas Cort (RETIRED) gentoo-dev 2006-09-07 04:00:53 UTC
Created attachment 96271 [details]

96254: 1.2.0-cid-overflows.patch doesn't work.
Comment 17 Donnie Berkholz (RETIRED) gentoo-dev 2006-09-07 09:37:32 UTC
Created attachment 96288 [details, diff]

Hrm. not sure how that happened... that was the diff between the two patches. Anyhow here's the right one.
Comment 18 Thomas Cort (RETIRED) gentoo-dev 2006-09-07 10:31:09 UTC
Created attachment 96295 [details, diff]

Attachment #96288 [details, diff] (1.2.0-cid-overflows.patch) fails with "No file to patch" because the paths in the patch begin with "lib/font" instead of "libXfont-1.2.0/src".

The attached patch is the same as Attachment #96288 [details, diff], but it replaces "lib/font" with "libXfont-1.2.0/src".
Comment 19 Thomas Cort (RETIRED) gentoo-dev 2006-09-07 11:20:58 UTC
looks good on amd64.
Comment 20 Joshua Jackson (RETIRED) gentoo-dev 2006-09-07 11:59:55 UTC
Appears to work correctly on x86 as well, so it can be marked when everyone else is
Comment 21 Gustavo Zacarias (RETIRED) gentoo-dev 2006-09-07 12:52:36 UTC
sparc looks fine.
Comment 22 Tobias Scherbaum (RETIRED) gentoo-dev 2006-09-07 23:20:55 UTC
looks good on ppc
Comment 23 René Nussbaumer (RETIRED) gentoo-dev 2006-09-08 13:02:12 UTC
looks good on hppa
Comment 24 Wolf Giesen (RETIRED) gentoo-dev 2006-09-11 06:00:38 UTC
Embargo time ends tomorrow. To be able to get it out we need word from 

- alpha
- ppc64 (just say you're okay with the latest patch, too :-)
Comment 25 Markus Rothe (RETIRED) gentoo-dev 2006-09-11 07:04:04 UTC
yes, latest patch okay on ppc64, too.
Comment 26 Thomas Cort (RETIRED) gentoo-dev 2006-09-11 07:39:45 UTC
(In reply to comment #24)
> Embargo time ends tomorrow. To be able to get it out we need word from 
> - alpha

Tested (with kloeri's permission) on alpha. Looks good on alpha.
Comment 27 Wolf Giesen (RETIRED) gentoo-dev 2006-09-12 02:22:00 UTC
That's all arches. No CVE yet?

Jaervosz (Donnie?), if you're sure about the embargo date, we could proceed with GLSA.
Comment 28 Donnie Berkholz (RETIRED) gentoo-dev 2006-09-12 10:49:45 UTC
I don't know anything further about embargo dates, there's nothing on the bugs so discussion must have taken place on lists.
Comment 29 Sune Kloppenborg Jeppesen (RETIRED) gentoo-dev 2006-09-12 10:56:39 UTC
The date was apparently chosen by the upstream Xorg Team and the initial report from iDEFENSE. 

So I guess the first public spot for this is:
Comment 30 Donnie Berkholz (RETIRED) gentoo-dev 2006-09-12 11:03:08 UTC
Upstream released, I'll bump in the tree.

Here's the advisory:

X.Org Security Advisory, September 12, 2006
Integer overflows in handling CID encoded Type1 fonts
CVE-ID: 2006-3739, 2006-3740


It may be possible for a user with the ability to set the X server
font path, by making it point to a malicious font, to cause
arbitrary code execution or denial of service on the X server.

Vulnerability details

The lack of validation of input data while parsing CID encoded Type1
fonts in the "type1" module may cause some integer overflows while
computing the size of allocated data buffers when parsing a
font. Arbitrary code embedded in the malicious font can then be
executed by the X server.

To exploit these vulnerabilities, the ability to connect to the X server
in order to execute 'xset fp+' or the equivalent is required.

CVE-ID 2006-3740 describes a vulnerability in the scan_cidfont()
function in Type1/scanfont.c, while CVE ID 2006-3739 describes similar
problems in the CIDADM() function in Type1/afm.c.

Affected versions

All X servers using the "type1" font module with CID font support are
vulnerable to this issue. This includes all X.Org versions from 6.7.0
to 7.1 inclusive. Older versions are not supported by X.Org.


If no CID-encoded Type 1 fonts are used, the "type1" module can be
disabled and replaced by the "freetype" module in /etc/X11/xorg.conf.
The freetype module is able to use Type1 fonts with standard (non CID)
encoding as well as True Type fonts.

Also, systems with memory address space randomization are less likely
to be successfully compromised, as the most effective way to exploit
these vulnerabilities rely on fixed address space.


These issues have been fixed in libXfont 1.2.1
Comment 31 Sune Kloppenborg Jeppesen (RETIRED) gentoo-dev 2006-09-12 11:06:56 UTC
I was wrong. First one appears to be here:

Donnie just go ahead and commit the updates.
Comment 32 Raphael Marichez (Falco) (RETIRED) gentoo-dev 2006-09-12 11:56:30 UTC
mmm, and what about xorg 6.8 ?
Comment 33 Raphael Marichez (Falco) (RETIRED) gentoo-dev 2006-09-12 12:39:17 UTC
rerating since it's local root flaw.
Comment 34 Donnie Berkholz (RETIRED) gentoo-dev 2006-09-12 13:05:49 UTC
(In reply to comment #32)
> mmm, and what about xorg 6.8 ?
Comment 35 Donnie Berkholz (RETIRED) gentoo-dev 2006-09-12 13:17:23 UTC
libXfont is in the tree and stabled on all tested architectures. Should be good to GLSA whenever.
Comment 36 Donnie Berkholz (RETIRED) gentoo-dev 2006-09-12 13:17:54 UTC
Sorry, forgot to specify version -- >=1.2.2 is safe.
Comment 37 Sune Kloppenborg Jeppesen (RETIRED) gentoo-dev 2006-09-12 21:07:02 UTC
Thx for the version note Donnie!

Security please review draft a second time.
Comment 38 Matthias Geerdsen (RETIRED) gentoo-dev 2006-09-13 02:21:51 UTC
Since the monolithic build is not supported anymore according to the -dev announce mail, I think it should either be masked or marked unstable to make that clear, to comply with policy and to make it clearer to users who don't look for such announcements.
Comment 39 Donnie Berkholz (RETIRED) gentoo-dev 2006-09-13 10:26:19 UTC
(In reply to comment #38)
> Since the monolithic build is not supported anymore according to the -dev
> announce mail, I think it should either be masked or marked unstable to make
> that clear, to comply with policy and to make it clearer to users who don't
> look for such announcements.

Sure, I'll mask it. I already added a USE flag to make it clear. Please take further discussion on this somewhere other than this bug.
Comment 40 Wolf Giesen (RETIRED) gentoo-dev 2006-09-13 10:55:39 UTC
Hm, this has left the building as GLSA 200609-07 ...

Thanks everybody.
Comment 41 genbug 2006-09-14 08:03:40 UTC
It would be very helpful to add this stop-gap measure to the glsa announcement from iDefence:


Access to the vulnerable code can be prevented by removing the entry 
for the Type1 font module from your Xservers configuration file, often
stored in /etc/X11 and named xorg.conf or XF86Config-4. To do this, 
remove the following line from the 'Module' section:

Load "type1"

This will prevent Type 1 fonts from loading, which may affect the 
appearance or operation of some applications.

This would at least let users stop the immediate threat whilst attacking the task of upgrading to modular X. A less than trivial job that will very likely require network access for howtos pkg etc and some fair ammount of time and effort. 

During this process the exploit would remain a serious vulnerability.

Comment 42 Wolf Giesen (RETIRED) gentoo-dev 2006-09-14 08:11:49 UTC
Sound argument. SecTeam, silent update?
Comment 43 Sune Kloppenborg Jeppesen (RETIRED) gentoo-dev 2006-09-14 08:28:09 UTC
I fail to see why we should update, we already have the following in the Workaround section:

Disable CID-encoded Type 1 fonts by removing the "type1" module and replacing it with the "freetype" module in xorg.conf.
Comment 44 Wolf Giesen (RETIRED) gentoo-dev 2006-09-14 08:42:13 UTC

Poked my own eyes too much, probably ^^
Comment 45 Wolf Giesen (RETIRED) gentoo-dev 2006-09-28 09:08:59 UTC