Linux 2.4.27 SECURITY BUG - TCP Local (probable Remote) Denial of Service
Greetings,
My apologies if this is to the wrong place - it happens to be the
first kernel bug I have found (or what appears to be one), and I'm not entirely sure how to properly inform the Linux community about it.
Anyway - on to the bug :)
==========================
Severity: HIGH
Title: KERNEL: TCP Local (probable remote) Denial of Service
Date: September 11, 2004
Synopsis
========
It appears there is a problem with sockets being reused before they are actually closed.
Description
============
I have intentionally not included very much detail, because it appears to me this could cause some serious havoc, and I'd rather not be responsible for the results. Details are available to kernel developers upon request to [email protected].
It appears there is a problem with sockets being reused before they are actually closed. Leaving them in TIME_WAIT until they expire. We were also able to leave them in CLOSE_WAIT, and they remained for days (assumably indefinitely)
The result of this ends up a bit unpredictable (or rather irreproducible). We are working on a commercial product including a proxy server, which ends up leaving the connections in CLOSE_WAIT state forever. When I wrote some proof of concept code, I was able to create a DOS condition, but I was only able to get the sockets to sit in TIME_WAIT state, so the kernel eventually cleared them. This is likely because I spent about 20 minutes on the proof of concept code, and have determined it can be abused, which is really all I was trying to accomplish :)
IMPACT:
=======
The issue ends up in the end that the kernel lets the connections sit in this state for a while, so once a ton of slots are taken up, it doesn't take much to keep the table full (several attempts every 10 - 20 seconds). occasionally the machine catches up, and the attack has to restart. The result however, is a 10 - 30 second delay in web transactions, and that was on a server with just me hitting it. On a busy web server, I wouldn't want to guess what it would be :)
** I was able to launch this attack as a regular user, and this machine ** has GrSecurity installed on it (CC'd to them too)
** You could compile this as a CGI, and take out about any Linux based ** web host (thus the reason for not releasing the PoC code.)
I tested it against telnetd (vulnerable), and sshd (didn't seem affected) mysqld (with the commercial product, it would run out of sockets, and require the offending process to be restarted to accept more), and Apache 1.3.29 (vulnerable)
The socket table looks like this while it is going on:
http://www.ancients.org/LG.txt
(it is 29,000+ lines, so I didn't put it here)
The bug doesn't appear to completely kill the ability to serve, but it slows it down to almost nothing.. On a busy web server, it would be virtually dead.
Proof of concept code:
======================
I will not be releasing this for the script kiddies to use :) If any of the kernel dev team wish to have it, please contact me. So long as I can verify you are a kernel maintainer, its all yours.
NOTE: Please send ALL correspondence regarding this to [admin <A> wolfpaw.com], do
not reply to this message, this address is simply one which receives a ton of list traffic. I could of course be off my rocker, and this not be a bug, but I don't think so :)
Regards,
D.
--------------------------------
Dale Corse
System Administrator
Wolfpaw Services Inc.
http://www.wolfpaw.net
(780) 474-4095
Close wait means the application locally has not closed the file descriptor, yet the remote end has sent a FIN.
This is %99 of the time an application bug.
But since you haven't provided much detail of the problem nobody will ever know exactly what you're talking about.
Please, do me and everyone else here on this list a real huge favor, don't post bug reports without all the details, you're just wasting everyone's time. If it's exploitable, even more reason to post every single detail so we can work on a fix if necessary as fast as possible.
Quoted 7 lines · Wolfpaw - Dale Corse
Greetings,
My apologies if this is to the wrong place - it happens to be the first kernel bug I have found (or what appears to be one), and I'm not entirely sure how to properly inform the Linux community about it.
Quoted 7 lines
Anyway - on to the bug :)
==========================
Severity: HIGH
Title: KERNEL: TCP Local (probable remote) Denial of Service
Date: September 11, 2004
Actually, it seems that the sockets that are not closing properly are the ones opened by your proof of concept code, *NOT* the server. The servers (mysql and Apache), close their sockets properly. I could verify this over a network. Locally, I got
tcp 0 0 192.168.53.2:41440 192.168.53.1:3306TIME_WAIT
tcp 0 0 192.168.53.2:41442 192.168.53.1:3306TIME_WAIT
tcp 0 0 192.168.53.2:41443 192.168.53.1:3306TIME_WAIT
tcp 0 0 192.168.53.2:41452 192.168.53.1:3306TIME_WAIT
tcp 0 0 192.168.53.2:41468 192.168.53.1:80TIME_WAIT
tcp 0 0 192.168.53.2:41441 192.168.53.1:80TIME_WAIT
tcp 0 0 192.168.53.2:41447 192.168.53.1:80TIME_WAIT
tcp 0 0 192.168.53.2:41444 192.168.53.1:80 TIME
etc..
But on the server, only 1 or two ESTABISHED entries, nothing more.
I don't see much of a DOS, except maybe to DOS a localhost. And you can do that already.
Quoted 6 lines
The socket table looks like this while it is going on:
http://www.ancients.org/LG.txt
(it is 29,000+ lines, so I didn't put it here)
Signature · 2 lines
Building your applications one byte at a time http://www.galacticasoftware.com
Quoted 5 lines
My apologies if this is to the wrong place - it happens to be the
first kernel bug I have found (or what appears to be one), and I'm not entirely sure how to properly inform the Linux community about it.
It's usually best to use the names / addressen in the MAINTAINERS file. Security issues like this are IMHO best first adressed to the maintainer of the code that is most likely to contain the bug.
I would suggest sending this to Dave Miller or Alexey Kuznetsov, both names which appear frequently when it comes to IP related stuff.
Regards,
Igmar
Close_wait is maintained by the server/application. Not releasing a resource is bad programming and would be seen as a bug in an app, not the kernel.
Read the good 'ol unix socket faq
http://www.informatik.hu-berlin.de/~mueller/dsm/kipper.york.ac.uk/vic/sock-f
aq/html/unix-socket-faq-2.html
If you google around a bit you'll see other people who have discussed this issue in depth.
Cheerio
Ivan
Tel: 0845 345 0919
Xtraordinary Hosting, 6 The Clocktower, South Gyle, Edinburgh, EH12 9LB
http://www.xtrahost.co.uk
-----Original Message-----
From: Wolfpaw - Dale Corse [mailto:[email protected]]
Sent: 11 September 2004 22:42
To: [email protected]
Cc: [email protected]; [email protected]
Subject: Linux 2.4.27 SECURITY BUG - TCP Local (probable Remote) Denial of Service
Greetings,
My apologies if this is to the wrong place - it happens to be the
first kernel bug I have found (or what appears to be one), and I'm not entirely sure how to properly inform the Linux community about it.
Anyway - on to the bug :)
==========================
Severity: HIGH
Title: KERNEL: TCP Local (probable remote) Denial of Service
Date: September 11, 2004
Synopsis
========
It appears there is a problem with sockets being reused before they are actually closed.
Description
============
I have intentionally not included very much detail, because it appears to me this could cause some serious havoc, and I'd rather not be responsible
for the results. Details are available to kernel developers upon request to [email protected].
It appears there is a problem with sockets being reused before they are actually closed. Leaving them in TIME_WAIT until they expire. We were also able to leave them in CLOSE_WAIT, and they remained for days (assumably indefinitely)
The result of this ends up a bit unpredictable (or rather irreproducible). We are working on a commercial product including a proxy server, which ends up leaving the connections in CLOSE_WAIT state forever. When I wrote some proof of concept code, I was able to create a DOS condition, but I was only able to get the sockets to sit in TIME_WAIT state, so the kernel eventually cleared them. This is likely because I spent about 20 minutes on the proof of concept code, and have determined it can be abused, which is really all I was trying to accomplish :)
IMPACT:
=======
The issue ends up in the end that the kernel lets the connections sit in this state for a while, so once a ton of slots are taken up, it doesn't take much to keep the table full (several attempts every 10 - 20 seconds). occasionally the machine catches up, and the attack has to restart. The result however, is a 10 - 30 second delay in web transactions, and that was on a server with just me hitting it. On a busy web server, I wouldn't want to guess what it would be :)
** I was able to launch this attack as a regular user, and this machine ** has GrSecurity installed on it (CC'd to them too)
** You could compile this as a CGI, and take out about any Linux based ** web host (thus the reason for not releasing the PoC code.)
I tested it against telnetd (vulnerable), and sshd (didn't seem affected) mysqld (with the commercial product, it would run out of sockets, and require
the offending process to be restarted to accept more), and Apache 1.3.29 (vulnerable)
The socket table looks like this while it is going on:
http://www.ancients.org/LG.txt
(it is 29,000+ lines, so I didn't put it here)
The bug doesn't appear to completely kill the ability to serve, but it slows it down to almost nothing.. On a busy web server, it would be virtually dead.
Proof of concept code:
======================
I will not be releasing this for the script kiddies to use :) If any of the kernel dev team wish to have it, please contact me. So long as I can verify you are a kernel maintainer, its all yours.
NOTE: Please send ALL correspondence regarding this to [admin <A> wolfpaw.com], do
not reply to this message, this address is simply one which receives a
ton of list traffic. I could of course be off my rocker, and this not be a bug, but I don't think so :)
Regards,
D.
--------------------------------
Dale Corse
System Administrator
Wolfpaw Services Inc.
http://www.wolfpaw.net
(780) 474-4095