Bug 145129 - CAN-2004-1125 xpdf buffer overflow
Summary: CAN-2004-1125 xpdf buffer overflow
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: tetex
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jindrich Novy
QA Contact: David Lawrence
URL:
Whiteboard: impact=moderate,public=20041221
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-01-14 16:55 UTC by Josh Bressers
Modified: 2013-07-02 23:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-04-01 14:39:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:354 0 normal SHIPPED_LIVE Moderate: tetex security update 2005-04-01 05:00:00 UTC

Description Josh Bressers 2005-01-14 16:55:37 UTC 
*** This bug has been split off bug 143499 ***

------- Original comment by Josh Bressers (Security Response Team) on 2004.12.21
13:15 -------

iDEFENSE has reported a buffer overflow issue in xpdf 3.  This issue
also affects the xpdf in RHEL3.

http://www.idefense.com/application/poi/display?id=172&type=vulnerabilities&flashstatus=true

The advisory references a patch to fix this issue.


This issue should also affect RHEL2.1
Comment 1 Jindrich Novy 2005-01-15 07:42:08 UTC 
Hello Josh,

I have noticed that RHEL2.1 is also affected when you informed me
about the CAN-2004-1125 some time ago. Patch to fix this is now
applied in both RHEL2.1 and RHEL3 versions of tetex.
Comment 2 Josh Bressers 2005-04-01 14:39:23 UTC 
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 the 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.

http://rhn.redhat.com/errata/RHSA-2005-354.html
Note You need to log in before you can comment on or make changes to this bug.