Skip to contentSkip to conversation

Linux 2.4.27 SECURITY BUG - TCP Local (probable Remote) Denial of Service

DISCUSSION Wolfpaw - Dale Corse 1 participant 1 message Sep 12, 2004 1 message not in the archive

lore
Share & tools
lore
#1 lore raw
In reply to a message not in the archive

David,

Quoted 8 lines

If the application doesn't close it's file descriptors there is absolutely nothing the kernel can do about it.

It's a resource leak, plain and simple.

Quoted 1 line

That being said - below is a the proper description, and

the code used

Quoted 8 lines
Quoted 2 lines

to exploit it. Hope it helps. This version is not the one which invokes the CLOSE_WAIT state, but rather the TIME_WAIT one,

I am not

Quoted 1 line

able to publish the source code for the CLOSE_WAIT bug.

There is nothing wrong with creating tons of TIME_WAIT sockets, they simply time out after 60 seconds (unless hit by a RESET packet or similar). This is how TCP works.

I am aware of that, you are missing the point. The point is the part where the socket is reused before it is completely closed, the end result being the daemon its pointed at keeps the connection open, and thus ends up in a DOS condition.

Please do me a favor, and read the bug before you comment.

Quoted 11 lines
Quoted 2 lines

The log however clearly shows that a mysql descriptor is

closed, and

Quoted 1 line

then used immediately again by the socket call, which

causes it never

Quoted 1 line

to end up getting closed. Linux apparently has either no

timeout for

Quoted 1 line

CLOSE_WAIT, or it's a very very long one.. Either way is a

bad thing.

Please do us all a favor and learn how TCP works.

A) Stop asking me for favors.
B) You have some serious aggression issues you need to work on :) I openly admitted not submitting issues before at the beginning of my first email, did I miss the part where it became required for you to turn into an asshole? :) I can see why people would toss exploits off to the zeroday groups, you get a more warm reception when you report a bug, and it ends up fixed in the end, instead of overrun with excuses :)

Quoted 7 lines

CLOSE_WAIT means simply that only one side of the TCP connection has done a close. Therefore the other end stays open until that side closes as well.

There is no way to "time things out" or release the state.

This is your "godly developer answer" to this bug? Ok, well, so I am to assume that this is the mission of the kernel:

A) All software must run perfectly, because we "can't do anything about resource leaks"
B) The internet is perfect, and there are no problems with TCP, so we can't add a timeout for CLOSE_WAIT, we must just leave it there forever. Forget the fact it could potentially bring the server, or the daemon it is speaking to down to its knees.
C) Don't submit bugs, because David likes to tell you that you know nothing, and "as a favor" to please go and find out what the hell your talking about. He obviously knows everything, so please, stop insulting his mailing list.

Is that correct? Here and I thought the job of the operating system was to deal with issues such as this. If this is indeed where Linux is headed, I fear the internet may be in a good deal of trouble.

For the record, I believe Microsoft Windows, and FreeBSD both have timeouts for this TCP State. But, I better go learn how they work, before I make such a comment.

Regards,
Dale.