mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: "nashleon@gmx.de" <nashleon@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is there any Buffer overflow attack mechanism that can break a	vulnerable server without breaking the ongoing connection?
Date: Tue, 27 Dec 2005 15:23:30 +0100	[thread overview]
Message-ID: <1135693411.2926.25.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <43B14D1A.8010608@gmx.de>

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.



      reply	other threads:[~2005-12-27 14:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-26 20:47 Xin Zhao
2005-12-26 20:51 ` Arjan van de Ven
2005-12-27 14:18   ` nashleon
2005-12-27 14:23     ` Arjan van de Ven [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1135693411.2926.25.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nashleon@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®