Bug 186057 - CVE-2006-1242 Linux zero IP ID vulnerability?
CVE-2006-1242 Linux zero IP ID vulnerability?
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Thomas Graf
Brian Brock
: Security
Depends On:
Blocks: 181409
  Show dependency treegraph
Reported: 2006-03-21 08:10 EST by Marcel Holtmann
Modified: 2014-06-18 04:28 EDT (History)
4 users (show)

See Also:
Fixed In Version: RHSA-2006-0575
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-10 18:50:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Marcel Holtmann 2006-03-21 08:10:06 EST
Interesting behaviour of some Linux kernels that may be exploited by a remote
attacker to abuse the ID field of IP packets, effectively bypassing the zero IP
ID in DF packets countermeasure implemented since 2.4.8 (IIRC).

Comment 1 David Miller 2006-03-22 15:47:35 EST
The code paths for sending TCP packets when we have a socket and when
we don't have one are different, and in fact this is unavoidable.

When we send a reset because we don't have a TCP socket that matches,
we have to use tcp_v4_send_reset(), which uses the ip_send_reply()
framework using the system-wide "tcp_socket" that is used for sending
packets when we have no associated socket.

SYN+ACK responses, go through yet another interface, ip_build_and_send_pkt()
via tcp_v4_send_synack().

We could pass a flag into ip_build_and_send_pkt() to tell it to not use a
non-zero IP ID when the DF bit is set.  Actually, scratch that, it should be
using the function "ip_select_ident_more()" just like ip_build_xmit() does.

That would solve the problem.

FWIW I don't see this as much of a real security problem, and by fixing it
we'll make Linux versions even more specifically identifyable remotely :)
Comment 2 Marcel Holtmann 2006-03-23 04:02:12 EST
According to Chris Wright the latest vanilla kernel contains a fix for it:

Comment 3 David Miller 2006-03-23 04:16:36 EST
Right, I pushed that to 2.6.17 and 2.6.x -stable.

Vanilla 2.4.x does not have the problem, but our RHEL3 2.4.x does
because it contains the IPSEC backport.
Comment 4 Thomas Graf 2006-03-24 09:34:12 EST
RHEL4 is not vulnerable to this with the default firewall enabled, at least not
the case documented. Naturally we should include the fix for cases where it is
Comment 7 Jason Baron 2006-04-06 21:52:30 EDT
committed in stream U4 build 34.14. A test kernel with this patch is available
from http://people.redhat.com/~jbaron/rhel4/
Comment 8 Bob Johnson 2006-04-11 13:13:34 EDT
This issue is on Red Hat Engineering's list of planned work items 
for the upcoming Red Hat Enterprise Linux 4.4 release.  Engineering 
resources have been assigned and barring unforeseen circumstances, Red 
Hat intends to include this item in the 4.4 release.
Comment 10 Mike Gahagan 2006-07-14 17:09:22 EDT
Patch is in -42.EL.
Comment 12 Red Hat Bugzilla 2006-08-10 18:50: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.