Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 162903 - CAN-2002-1914 dump denial of service
Summary: CAN-2002-1914 dump denial of service
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: dump
Version: 2.1
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jindrich Novy
QA Contact: Ben Levenson
Whiteboard: impact=low,public=20020717,source=cve
Depends On:
TreeView+ depends on / blocked
Reported: 2005-07-11 15:44 UTC by Josh Bressers
Modified: 2013-07-02 23:08 UTC (History)
2 users (show)

Fixed In Version: RHSA-2005-583
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-08-03 14:12:19 UTC
Target Upstream Version:

Attachments (Terms of Use)
Patch taken from upstream CVS (1.69 KB, patch)
2005-07-11 15:46 UTC, Josh Bressers
no flags Details | Diff

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:583 0 normal SHIPPED_LIVE Low: dump security update 2005-08-03 04:00:00 UTC

Description Josh Bressers 2005-07-11 15:44:42 UTC
dump 0.4 b10 through b29 allows local users to cause a denial of service
(execution prevention) by using flock() to lock the /etc/dumpdates file.

More information regarding this issue is here:

Comment 1 Josh Bressers 2005-07-11 15:46:47 UTC
Created attachment 116609 [details]
Patch taken from upstream CVS

Comment 2 Jindrich Novy 2005-07-12 08:19:07 UTC
Josh, thanks for the patch, it's now applied and errata is comming up.

Comment 3 Red Hat Bugzilla 2005-08-03 14:12:20 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.


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