Bug 486052 (CVE-2009-0577) - CVE-2009-0577 cups-CVE-2008-3640.patch has been corrupted.
Summary: CVE-2009-0577 cups-CVE-2008-3640.patch has been corrupted.
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2009-0577
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 486101
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-18 01:47 UTC by keishi.sonoda
Modified: 2019-09-29 12:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-02-19 18:44:41 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2009:0308 normal SHIPPED_LIVE Important: cups security update 2009-02-19 17:43:11 UTC

Description keishi.sonoda 2009-02-18 01:47:10 UTC
Description of problem:
rpmbuild cannot apply cups-CVE-2008-3640.patch due to the patch corruption.

Version-Release number of selected component (if applicable):
cups-1.1.17-13.3.54.src.rpm
cups-1.1.17-13.3.55.src.rpm

How reproducible:
always

Steps to Reproduce:
1. rpm -i cups-1.1.17-13.3.54.src.rpm
2. rpmbuild -bp /usr/src/redhat/SPEC/cups.spec
  
Actual results:
error: File /usr/src/redhat/SOURCES/cups-CVE-2008-3640.patch is smaller than 4 bytes

Expected results:
Unpack the sources and apply the patch.

Additional info:

Comment 1 Josh Bressers 2009-02-18 12:34:15 UTC
We will assign this issue CVE-2009-0577.

Comment 3 Mark J. Cox 2009-02-19 08:18:49 UTC
Thank you for reporting this issue.  We will produce a security update to address this for Red Hat Enterprise Linux 3.  Note that Red Hat Enterprise Linux 4 and 5 already contain the correct fix for CVE-2008-3640 and do not need to be updated.

Comment 4 Red Hat Product Security 2009-02-19 18:44:41 UTC
This issue was addressed in:

Red Hat Enterprise Linux:
  http://rhn.redhat.com/errata/RHSA-2009-0308.html


Note You need to log in before you can comment on or make changes to this bug.