Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 3 product line. The current stable release is 3.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 126716

Summary: CAN-2004-0497 inode_change_ok missing checks allows GID changes
Product: Red Hat Enterprise Linux 3 Reporter: Mark J. Cox <mjc>
Component: kernelAssignee: Ernie Petrides <petrides>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: aviro, petrides, riel
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-07-02 08:21:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 116727    
Attachments:
Description Flags
Original patch (from SUSE, ACK'd by Al Viro) none

Description Mark J. Cox 2004-06-25 08:53:48 UTC 
An audit by SUSE found a missing "must be owner of the file" check in
inode_change_ok().  In the 2.6 kernel this allows a local user to be
able to change the groupid of any object (except those setgid) by
using chown.  In the 2.4 kernel is is exploitable only via a kernel
nfsd export where the server will grant requests to change GID when it
shouldn't.

SUSE suggested an embargo date of Jul14 1600MEST but this has been
adjusted to Jun29 1600MEST.
Comment 1 Mark J. Cox 2004-06-25 08:57:22 UTC 
Created attachment 101396 [details]
Original patch (from SUSE, ACK'd by Al Viro)
Comment 2 Ernie Petrides 2004-06-30 05:06:39 UTC 
A fix for this problem has been committed to the RHEL3 E3 patch
pool this afternoon (in kernel version 2.4.21-15.0.3.EL) and a
Red Hat Security Advisory (RHSA-2004:360) has been prepared.

I'll leave this bug in ASSIGNED state until the same fix has
been committed to the RHEL3 U3 patch pool (later this week).
Comment 3 Mark J. Cox 2004-06-30 07:42:10 UTC 
Embargo was moved to Friday Jul02 at 0800UTC
Comment 4 Mark J. Cox 2004-07-02 07:59:13 UTC 
Removing embargo
Comment 5 Mark J. Cox 2004-07-02 08:21:34 UTC 
An errata 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-2004-360.html
Comment 6 Ernie Petrides 2004-07-02 21:58:47 UTC 
A fix for this problem has just been committed to the RHEL3 U3
patch pool this afternoon (in kernel version 2.4.21-15.19.EL).