Bug 56024 – Fix for bug #5903 (race condition in lpr) is incomplete--the race condition still exists

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 56024 - Fix for bug #5903 (race condition in lpr) is incomplete--the race condition still exists

Summary:	Fix for bug #5903 (race condition in lpr) is incomplete--the race condition s...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	lpr (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Tim Waugh
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:	Security

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-11-10 20:41 EST by Brian Chess
Modified:	2007-04-18 12:38 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-12-18 17:43:22 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Brian Chess 2001-11-10 20:41:10 EST

bug #5903 (race condition in lpr) was fixed by adding calls to seteuid()
before the calls to open().  The problem is that the value returned from
seteuid() isn't checked.  If seteuid fails, the race condition is still
there.  Why would seteuid() fail, you ask?  Check out
http://www.securityfocus.com/bid/1322 for an example.

Comment 1 Tim Waugh 2002-01-15 11:47:05 EST

This kernel bug has already been addressed by a kernel advisory.

Comment 2 Brian Chess 2002-01-15 14:37:54 EST

The kernal bug that I pointed out was an example.  If you don't fix the problem 
in lpr, it will be suseptable to all future problems of that type.

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