mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Xin Zhao <uszhaoxin@gmail.com>
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: Mon, 26 Dec 2005 21:51:21 +0100	[thread overview]
Message-ID: <1135630282.3910.8.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <4ae3c140512261247p612146f5w6ad8bf474f4ebfd5@mail.gmail.com>

On Mon, 2005-12-26 at 15:47 -0500, Xin Zhao wrote:
> We are working on a mechanism that monitors the connections of a
> server and detects potential intrusions via broken connection
> (incoming request received, but no reply).  We want to thoroughly
> understand the possibility of mounting a buffer overflow attack
> against a server process without cutting off the connection.

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


  reply	other threads:[~2005-12-26 20:51 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 [this message]
2005-12-27 14:18   ` nashleon
2005-12-27 14:23     ` Arjan van de Ven

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=1135630282.3910.8.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=uszhaoxin@gmail.com \
    /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®