CVE-2005-3191: Buffer Overflow

Published Dec 7, 2005
·
Updated

Multiple heap-based buffer overflows in the (1) DCTStream::readProgressiveSOF and (2) DCTStream::readBaselineSOF functions in the DCT stream parsing code (Stream.cc) in xpdf 3.01 and earlier, as used in products such as (a) Poppler, (b) teTeX, (c) KDE kpdf, (d) pdftohtml, (e) KOffice KWord, (f) CUPS, and (g) libextractor allow user-assisted attackers to cause a denial of service (heap corruption) and possibly execute arbitrary code via a crafted PDF file with an out-of-range number of components (numComps), which is used as an array index.

Affected Software

15 affected components
xpdf Xpdf=0.90
xpdf Xpdf=0.91
xpdf Xpdf=0.92
xpdf Xpdf=0.93
xpdf Xpdf=1.0
xpdf Xpdf=1.0a
xpdf Xpdf=1.1
xpdf Xpdf=2.0
xpdf Xpdf=2.1
xpdf Xpdf=2.2
xpdf Xpdf=2.3
xpdf Xpdf=3.0
xpdf Xpdf=3.0.1
xpdf Xpdf=3.0_pl2
xpdf Xpdf=3.0_pl3

Event History

Dec 7, 2005
CVE Published
01:03 AM
CVE Published
via MITRE·06:00 AM
Data Sourced
via MITRE·06:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2005-3191?

CVE-2005-3191 is considered to have a high severity due to multiple heap-based buffer overflows that can be exploited.

2

How do I fix CVE-2005-3191?

To fix CVE-2005-3191, you should upgrade to a version of Xpdf that is newer than 3.01, which no longer contains this vulnerability.

3

What software is affected by CVE-2005-3191?

CVE-2005-3191 affects multiple software products including Xpdf, Poppler, and KDE kpdf among others.

4

What are the potential impacts of exploiting CVE-2005-3191?

Exploiting CVE-2005-3191 may allow an attacker to execute arbitrary code or crash the application.

5

When was CVE-2005-3191 disclosed?

CVE-2005-3191 was publicly disclosed in 2005, prompting the need for immediate security updates.

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