Subject: Re: Is there any Buffer overflow attack mechanism that can break
	a	vulnerable server without breaking the ongoing connection?
From: Arjan van de Ven <arjan@infradead.org>
To: "nashleon@gmx.de" <nashleon@gmx.de>
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <43B14D1A.8010608@gmx.de>
References: <4ae3c140512261247p612146f5w6ad8bf474f4ebfd5@mail.gmail.com>
	 <1135630282.3910.8.camel@laptopd505.fenrus.org>  <43B14D1A.8010608@gmx.de>
Content-Type: text/plain
Date: Tue, 27 Dec 2005 15:23:30 +0100
Message-Id: <1135693411.2926.25.camel@laptopd505.fenrus.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1172
Lines: 33

On Tue, 2005-12-27 at 12:18 -0200, nashleon@gmx.de wrote:
> Arjan van de Ven escreveu:
> 
> >buffer overflows do not break connections, and as such I think you are
> >out of luck.
> >Having said that.. on modern linux distros it's pretty hard to do a
> >buffer overflow exploit nowadays (NX[1] to make stacks non-executable,
> >randomisations, compiler based detection (via FORTIFY_SOURCE and/or
> >-fstackprotector)... add all those together and it's certainly not easy
> >to do this....
> >
> >
> >
> >[1] or emulations of NX such as segment limits techniques
> >
> >  
> >
> 
> Hello!
> 
> Locally is very simple to exploit buffer overflows in the linux kernel. 

sure kernel space is a whole different kettle of fish. The good news
there however is that in kernel space it's rather rare to work with
buffers on the stack (by virtue of only having a really tiny stack in
the first place). Not impossible but at least rare.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/