Bug 166131 - CAN-2005-2555 IPSEC lacks restrictions
CAN-2005-2555 IPSEC lacks restrictions
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: John W. Linville
Brian Brock
: Security
Depends On:
Blocks: 156322
  Show dependency treegraph
Reported: 2005-08-17 04:35 EDT by Mark J. Cox
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version: RHSA-2005-514
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-10-05 09:51:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
jwltest-sock-policy-cap.patch (752 bytes, patch)
2005-08-17 13:54 EDT, John W. Linville
no flags Details | Diff
jwltest-sock-policy-cap.patch (748 bytes, patch)
2005-08-17 14:15 EDT, John W. Linville
no flags Details | Diff

  None (edit)
Description Mark J. Cox 2005-08-17 04:35:19 EDT
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:

Comment 1 John W. Linville 2005-08-17 13:54:24 EDT
Created attachment 117851 [details]
Comment 2 John W. Linville 2005-08-17 14:13:59 EDT
Test kernels available here: 
Test reports welcome... :-) 
Comment 3 John W. Linville 2005-08-17 14:15:08 EDT
Created attachment 117854 [details]

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


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