From: IceDane <icedane@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Stack protection mechanisms in 4.0+/4.1.2?
Date: Sat, 13 Oct 2007 22:10:00 -0000 [thread overview]
Message-ID: <4711149D.1040906@gmail.com> (raw)
Hey there.
A course in my school involves exploitation of various vulnerabilities,
such as buffer overflows and format string vulnerabilities and so on.
I'm currently running kbuntu, latest version, which comes with gcc 4.1.2
stock. If I compile a vulnerable program(A simple strcpy of argv[1] to a
small buffer) and then attempt to execute an exploit, no matter what i
do, it fails.
I realize that the ubuntu gcc 4.1.2 compiles with the -fstack-protector
as default, however, even if I use -fno-stack-protector, the problem
still prevails.
All kernels since 2.6 also come with virtual address space randomization
as default, and I've disabled that.
Anyway, I found something that said if you installed gcc 3.3, you'd be
fine. I try that, and voila, exploit executes accordingly.
Now, I ask - What is it, other than the -fstack-protector flag, which
can disable buffer overflow exploits like that in gcc?
P.S. I just installed ubuntu to see if the problem prevailed here - I
was using slack 12.0 just yesterday, with the same version of GCC, and I
had the exact same problem.
All help greatly appreciated.
next reply other threads:[~2007-10-13 18:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-13 22:10 IceDane [this message]
2007-10-15 11:14 ` Andrew Haley
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=4711149D.1040906@gmail.com \
--to=icedane@gmail.com \
--cc=gcc-help@gcc.gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).