Bug 165560 - CAN-2005-2456 IPSEC overflow
Summary: CAN-2005-2456 IPSEC overflow
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel   
(Show other bugs)
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: David Miller
QA Contact: Brian Brock
Whiteboard: impact=important,public=20050725,sour...
Keywords: Security
: 165138 (view as bug list)
Depends On:
Blocks: 156322
TreeView+ depends on / blocked
Reported: 2005-08-10 14:23 UTC by Mark J. Cox
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version: RHSA-2005-514
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-10-05 13:50:11 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:514 qe-ready SHIPPED_LIVE Important: Updated kernel packages available for Red Hat Enterprise Linux 4 Update 2 2005-10-05 04:00:00 UTC

Description Mark J. Cox 2005-08-10 14:23:14 UTC
When a user specified IPSEC rule to compile is given, we don't check
the bounds of the direction, leading to overflows of the in-socket
IPSEC rule array.  This could allow a local unprivileged user to cause memory

Fixed upstream here on 20050726

See the following threads for a test program and more desciprtion


Note that a fix for this is already committed for U2 in linux-2.6.12-network.patch

Comment 4 Mark J. Cox 2005-08-30 08:31:42 UTC
*** Bug 165138 has been marked as a duplicate of this bug. ***

Comment 6 Red Hat Bugzilla 2005-10-05 13:50:11 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.


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