This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours
Bug 162903 - CAN-2002-1914 dump denial of service
CAN-2002-1914 dump denial of service
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: dump (Show other bugs)
2.1
All Linux
medium Severity low
: ---
: ---
Assigned To: Jindrich Novy
Ben Levenson
impact=low,public=20020717,source=cve
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-07-11 11:44 EDT by Josh Bressers
Modified: 2013-07-02 19:08 EDT (History)
2 users (show)

See Also:
Fixed In Version: RHSA-2005-583
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-08-03 10:12:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


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

  None (edit)
Description Josh Bressers 2005-07-11 11:44:42 EDT
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:
http://archives.neohapsis.com/archives/bugtraq/2002-07/0204.html
Comment 1 Josh Bressers 2005-07-11 11:46:47 EDT
Created attachment 116609 [details]
Patch taken from upstream CVS
Comment 2 Jindrich Novy 2005-07-12 04:19:07 EDT
Josh, thanks for the patch, it's now applied and errata is comming up.
Comment 3 Red Hat Bugzilla 2005-08-03 10:12:20 EDT
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-583.html

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