Re: GetPC code (was: Shellcode from ASCII)

From: Berend-Jan Wever (SkyLined_at_edup.tudelft.nl)
Date: 07/01/03

  • Next message: Costin Ionescu: "Re: GetPC code (was: Shellcode from ASCII)" 
    Date: Tue, 01 Jul 2003 09:59:43 +0200
To: vuln-dev@securityfocus.com

    ----- Original Message -----
    From: "Gerardo Richarte" <gera@corest.com>
    To: <vuln-dev@securityfocus.com>
    Sent: Monday, June 30, 2003 16:11
    Subject: Re: GetPC code (was: Shellcode from ASCII)

    > Berend-Jan Wever wrote:
    >
    > Well... nop slides are not a problem: if you have some approximation of
    > where in memory the shellcode may be, you can always scan for it, and get
    > the right address where it starts, but if you don't know where it is, you
    may
    > make the process crash while scanning for the shellcode in memory... You
    > could also change nops for inc %eax (or any other register), and then, if
    > you knew the initial value for eax, you would know how many "nops" were
    > executing before the first byte of the shellcode :-)
    I don't see how you are going to scan memory if you can not make your code
    loop (jmp-ing back uses a negative dislocations, which is >0x80 and not
    alpha numeric)
    The "counting" nopslide is a great idear, and since I was going to get the
    baseaddress of the shellcode from a register, you can use the "inc %ebx" (or
    any other register except eax) too ;)

    > On the other hand, there ARE some exploits where you don't know the
    > address of the shellcode, mainly because the vulnerable program is putting
    > it for you in the right place (wu-ftp's ~{, system V login's, and some ssh
    > I remember could be done like this). On that cases you probably can't know
    > the address of your shellcode... but still, there may be some other means
    of
    > getting it (and not just mov %eip, %eax).
    If it's on the stack, esp or ebp can be used and possibly some other
    registers.
    If it's on the heap, you might be able to find some static pointer or
    pointer on the stack the gives you the baseaddress of your shellcode.
    Too bad you can not add or sub an offset from a register.

    >
    > > PS. hi gera, halvar ;)
    >
    > :-)
    >
    > gera
     :P:p:P hehehe

    SkyLined

    PS. "Alpha", my _uppercase_ alphanumeric shellcode generator is a few days
    away from completion ;)

    PS2. The latest IE BoF can be exploited ;)
    (let me know if you want it Sunil)

  • Next message: Costin Ionescu: "Re: GetPC code (was: Shellcode from ASCII)"

    Relevant Pages

    • Re: [Full-disclosure] Mercur IMAPD 5.0 SP3 DoS Exploit or more?
      ... A common exploitation solutions is placing the rest of shellcode ... somewhere else on the memory. ... enough to simply recv() the rest of shellcode. ... overwriting saved EIP with recvaddress. ...
      (Full-Disclosure)
    • Re: DEFCON 16 and Hacking OpenVMS
      ... Therefore the code injected after the overflow executes some other ... Since there is no such thing as "shellcode" in VMS, ... area of memory to be executable and then branch to it. ... There sure is shellcode for OpenVMS, ...
      (comp.os.vms)
    • Re: Getting Base Address using the Structured Exception Handler
      ... But you can use SEH to search ... through all of memory in search of anything really. ... smaller than almost any other kind of robust Win32 shellcode (CANVAS's is ...
      (Vuln-Dev)
    • [TOOL] Windows Reverse Shellcode (under 300 Bytes, no spaces, no NULLs)
      ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... The following shellcode is a reverse shell shellcode for Windows. ... the script does fast JMP ESP search in memory for different DLLs ... DWORD FindESP(LPSTR startaddr, int dobreak) ...
      (Securiteam)
    • RE: Automatic discovery of shellcode address
      ... Erm, correct me if I'm wrong, but the idea of placing your shellcode ... buffer with the address of the shellcode is a very old idea and very ... If this is vulnerable you'd see something like "cannot access memory ... you're overflowing is, (in the case of sprintf, strcpy etc), you ...
      (Vuln-Dev)