[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Changes in Aleph1 Smashing the Stack...
- To: Florencio Cano <email@example.com>
- Subject: Re: Changes in Aleph1 Smashing the Stack...
- From: Christian North <firstname.lastname@example.org>
- Date: Mon, 29 Nov 2004 14:19:50 -0600
- Cc: email@example.com
- Delivered-to: mailing list firstname.lastname@example.org
- Delivered-to: moderator for email@example.com
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=GcvrHwjHMqdrtmSl+iRU49z1IX55snWSFdz8BMSIvNevF3h66TkStUyA9XGDGw3GXlnc9h9DKAIX0ugPdxU4zcMi8OMQbXSHxxwDcjonhba/1LDylTeJt9DH1ZX81y/uzTyJ8Vjlg0wA1+PZb2z4jy55XjdWUkfg7OnPf8UEccM=
- In-reply-to: <20041126222812.E02A.FCANO@ono.com>
- List-help: <mailto:firstname.lastname@example.org>
- List-id: <vuln-dev.list-id.securityfocus.com>
- List-post: <mailto:email@example.com>
- List-subscribe: <mailto:firstname.lastname@example.org>
- List-unsubscribe: <mailto:email@example.com>
- Mailing-list: contact firstname.lastname@example.org; run by ezmlm
- References: <20041126222812.E02A.FCANO@ono.com>
- Reply-to: Christian North <email@example.com>
Use JMP and CALL with a label instead of the relative address. This
will use an 8 bit opval instead of a 32 bit fixed address. I believe
this will make your shellcode it will look like Aleph1's when
On Fri, 26 Nov 2004 22:31:37 +0100, Florencio Cano <firstname.lastname@example.org> wrote:
> I'm studying how buffer overflows work. While reading the famous article
> by Aleph1 Smashing the Stack for Fun and Profit I have got some problems.
> I think my problems are caused by changes in new versions of gcc so,
> where I can find information about how changes in new versions of gcc
> affect the stack when a function are called or how new versions affect
> the programming of bofs.
> Thanks in advance and sorry if the question is so basic.
> Florencio Cano <email@example.com>