All of lore.kernel.org
 help / color / mirror / Atom feed
From: "nashleon@gmx.de" <nashleon@gmx.de>
To: Arjan van de Ven <arjan@infradead.org>, 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 12:18:02 -0200	[thread overview]
Message-ID: <43B14D1A.8010608@gmx.de> (raw)
In-Reply-To: <1135630282.3910.8.camel@laptopd505.fenrus.org>

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. 
This protections is not
efective very well, so it's possible many attacks... It's possible to 
return in mmap() area,
overwrite values em syscall table and after that run malicious code 
using mmap() to allocate
data and many others schemes and techniques.

Linux is very robust and its resources is very good, but it is not yet 
the solution against buffer overflows.

Best Regards,

Nash Leon 

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-26 20:47 Is there any Buffer overflow attack mechanism that can break a vulnerable server without breaking the ongoing connection? Xin Zhao
2005-12-26 20:51 ` Arjan van de Ven
2005-12-27 14:18   ` nashleon [this message]
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=43B14D1A.8010608@gmx.de \
    --to=nashleon@gmx.de \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.