CVE-2009-3606: Buffer Overflow

Published Oct 2, 2009
·
Updated

Integer overflow in the PSOutputDev::doImageL1Sep function in Xpdf before 3.02pl4, and Poppler 0.x, as used in kdegraphics KPDF, might allow remote attackers to execute arbitrary code via a crafted PDF document that triggers a heap-based buffer overflow.

Other sources

xpdf's PSOutputDev::doImageL1Sep contains an integer overflow in the lineBuf buffer allocation:

4303 // allocate a line buffer 4304 lineBuf = (Guchar )gmalloc(4 width);

width is read from the input PDF file and can integer overflow / wrap when multiplied by 4, resulting in an insufficient memory allocation, leading to heap overflow.

Impact of this flaw is, however, quite limited. This affects PSOutputDev class used to write / convert PDF input to PS (PostScript) output. For GUI viewers, this is done e.g. when trying to print the file. Additionally, this requires non-default Level 1 separable PostScript language level to be used for the output file (specified via e.g. -level1sep command line option for pdftops, or psLevel configuration option in xpdfrc).

Red Hat

Affected Software

64 affected componentsFixes available
redhat/xpdf<1:2.02-17.el3
1:2.02-17.el3
redhat/gpdf<0:2.8.2-7.7.2.el4_7.4
0:2.8.2-7.7.2.el4_7.4
redhat/xpdf<1:3.00-22.el4_8.1
1:3.00-22.el4_8.1
redhat/poppler<0:0.5.4-4.4.el5_3.9
0:0.5.4-4.4.el5_3.9
redhat/kdegraphics<7:3.5.4-15.el5_4.2
7:3.5.4-15.el5_4.2
Foolabs Xpdf=3.02pl1
Foolabs Xpdf=3.02pl2
Foolabs Xpdf=3.02pl3
Glyphandcog Xpdfreader=3.00
Glyphandcog Xpdfreader=3.01
Glyphandcog Xpdfreader=3.02
Poppler Poppler=0.1
Poppler Poppler=0.1.1
Poppler Poppler=0.1.2
Poppler Poppler=0.2.0
Poppler Poppler=0.3.0
Poppler Poppler=0.3.1
Poppler Poppler=0.3.2
Poppler Poppler=0.3.3
Poppler Poppler=0.4.0
Poppler Poppler=0.4.1
Poppler Poppler=0.4.2
Poppler Poppler=0.4.3
Poppler Poppler=0.4.4
Poppler Poppler=0.5.0
Poppler Poppler=0.5.1
Poppler Poppler=0.5.2
Poppler Poppler=0.5.3
Poppler Poppler=0.5.4
Poppler Poppler=0.5.9
Poppler Poppler=0.6.0
Poppler Poppler=0.6.1
Poppler Poppler=0.6.2
Poppler Poppler=0.6.3
Poppler Poppler=0.6.4
Poppler Poppler=0.7.0
Poppler Poppler=0.7.1
Poppler Poppler=0.7.2
Poppler Poppler=0.7.3
Poppler Poppler=0.8.0
Poppler Poppler=0.8.1
Poppler Poppler=0.8.2
Poppler Poppler=0.8.3
Poppler Poppler=0.8.4
Poppler Poppler=0.8.6
Poppler Poppler=0.8.7
Poppler Poppler=0.9.0
Poppler Poppler=0.9.1
Poppler Poppler=0.9.2
Poppler Poppler=0.9.3
Poppler Poppler=0.10.0
Poppler Poppler=0.10.1
Poppler Poppler=0.10.2
Poppler Poppler=0.10.3
Poppler Poppler=0.10.4
Poppler Poppler=0.10.5
Poppler Poppler=0.10.6
Poppler Poppler=0.10.7
Poppler Poppler=0.11.0
Poppler Poppler=0.11.1
Poppler Poppler=0.11.2
Poppler Poppler=0.11.3
Poppler Poppler=0.12.0
KDE kpdf

Event History

Oct 2, 2009
Data Sourced
via Red Hat·09:22 AM
DescriptionSeverityAffected Software
Oct 14, 2009
CVE Published
via Red Hat·12:00 AM
Oct 21, 2009
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
Data Sourced
05:30 PM
DescriptionWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2009-3606?

CVE-2009-3606 has a high severity rating due to the potential for remote attackers to execute arbitrary code.

2

How do I fix CVE-2009-3606?

To fix CVE-2009-3606, update to the latest version of Xpdf or Poppler that addresses the vulnerability.

3

Which software is affected by CVE-2009-3606?

CVE-2009-3606 affects Xpdf versions prior to 3.02pl4, Poppler 0.x, and several other related packages.

4

What types of attacks can CVE-2009-3606 enable?

CVE-2009-3606 can enable remote attackers to exploit a crafted PDF document to perform code execution.

5

Is there a workaround for CVE-2009-3606?

A direct workaround for CVE-2009-3606 isn't well-documented, but avoiding the use of vulnerable software versions is advisable.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203