Bug 166131

Summary: CAN-2005-2555 IPSEC lacks restrictions
Product: Red Hat Enterprise Linux 4 Reporter: Mark J. Cox <mjc>
Component: kernelAssignee: John W. Linville <linville>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 4.0CC: jbaron
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: impact=important,public=20050806,source=cve,reported=20050806
Fixed In Version: RHSA-2005-514 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-10-05 13:51:07 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: 156322    
Attachments:
Description Flags
jwltest-sock-policy-cap.patch
none
jwltest-sock-policy-cap.patch none

Description Mark J. Cox 2005-08-17 08:35:19 UTC 
A flaw was discovered where xfrm_user_policy was not protected by CAP_NET_ADMIN.
 A local unprivileged user could use this flaw to bypass or create IPSEC
policies.  This is not believed to allow privilege escalation, but could lead to
a denial of service (since there is no upper bounds on creating policies).

A fix was committed to 2.6 to correct this issue:

http://linux.bkbits.net:8080/linux-2.6/cset@42f783aesxFQlEEg0e9GPi4oeVDHbA
Comment 1 John W. Linville 2005-08-17 17:54:24 UTC 
Created attachment 117851 [details]
jwltest-sock-policy-cap.patch
Comment 2 John W. Linville 2005-08-17 18:13:59 UTC 
Test kernels available here: 
 
   http://people.redhat.com/linville/kernels/rhel4/ 
 
Test reports welcome... :-)
Comment 3 John W. Linville 2005-08-17 18:15:08 UTC 
Created attachment 117854 [details]
jwltest-sock-policy-cap.patch

Should use the one generated for RHEL4...
Comment 8 Red Hat Bugzilla 2005-10-05 13:51:07 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.

http://rhn.redhat.com/errata/RHSA-2005-514.html