Skip to main content

SLAEx86 : Egg Hunter Shellcode

Egg Hunter is a technique that is used to run shellcode when the buffer space is too small to accommodate the shellcode.

So the concept of egg hunter is to put a unique string in the memory also known as "TAG" or "EGG" and we will search for the occurrence of this tag and just next to the tag we will put the shellcode. The egg hunter payload ( which is smaller in size compared to the payload ) will search for the tag and once it finds the tag, its control will jump to that location and thus execute the payload in the process

Algorithm for implementation

start()
     STEP 1 : store unique string in EBX
     STEP 2 : align() address and update in EDX
     STEP 3 : increase_address()
     STEP 4 : check_if_efault_occurred_while_accessing_the_memory()
                     if yes:
                              GOTO STEP 2
                   else:
                             STEP 5 : check if the memory location has the TAG value()
                                           if no:
                                                         GOTO STEP 3
                                           if yes:
                                                        check if next memory location has TAG value():
                                                        if yes:
                                                                 JUMP at that location
                                                        if no:
                                                                 STEP 3
                               
We need to ensure that whenever we are putting the shellcode inside the egghunter wrapper, we need to put the EGG / TAG twice in the shellcode.

Generated by r2
[0x08048060]> agfd _start > egghunter.dot
=> dot egghunter.dot -Tpng -o egghunter.png



C Wrapper

I have written a detailed post on how we can use this method to exploit a scenario when the buffer space is small.

Details can be found here : https://oxhat.blogspot.com/2018/04/why-do-we-need-egg-hunters.html

This blog post has been created for completing the requirements of SecurityTube Linux Assembly Expert Certification:
http://www.securitytube-training.com/online-courses/securitytube-linux-assembly-expert/
Student ID: PA-1191

Popular posts from this blog

KringleCon : Sans Holiday Hack 2018 Writeup

SANS HOLIDAY HACK 2018 Writeup , KRINGLECON The objectives  Orientation Challenge  Directory Browsing  de Bruijn Sequences  Data Repo Analysis  AD Privilege Discovery  Badge Manipulation  HR Incident Response  Network Traffic Forensics  Ransomware Recovery  Who Is Behind It All? First I go to Bushy Evergreen and try to solve the terminal challenge . Solving it is fairly easy , Escape_Key followed by  ":q" without quotes After this we move to the kiosk and solve the questions The question were based on the themes of previous Holiday Hack Challenges. Once we answer it correctly we get the flag. For this I visited Minty Candycane and I tried to solve the terminal challenge.  The application has command injection vulnerability , so injecting a system command with the server ip allows execution of the command. So first I perform an `ls` operation to list of the directory contents , followed by a cat of t

Linux Privilege Escalation : SUID Binaries

After my OSCP Lab days are over I decided to do a little research and learn more on Privilege Escalation as it is my weak area.So over some series of blog post I am going to share with you some information of what I have learnt so far. The methods mentioned over here are not my own. This is something what I have learnt by reading articles, blogs and solving CTFs SUID - Set User ID The binaries which has suid enabled, runs with elevated privileges. Suppose you are logged in as non root user, but this suid bit enabled binaries can run with root privileges. How does a SUID Bit enable binary looks like ? -r- s r-x---  1 hack-me-bak-cracked hack-me-bak         7160 Aug 11  2015 bak How to find all the SUID enabled binaries ? hack-me-bak2@challenge02:~$ find / -perm -u=s 2>/dev/null /bin/su /bin/fusermount /bin/umount /usr/lib/openssh/ssh-keysign /usr/lib/eject/dmcrypt-get-device /usr/lib/dbus-1.0/dbus-daemon-launch-helper /usr/bin/gpasswd /usr/bin/newgrp /usr/bin

Bluetooth Low Energy : Build, Recon,Enumerate and Attack !

Introduction In this post I will try to share some information on bluetooth low energy protocol. Bluetooth Low Energy ( BLE ) is Bluetooth 4.0.It has been widely used in creating "smart" devices like bulbs that can be controlled by mobile apps, or electrical switches that can be controlled by mobile apps. The terms Low Energy refers to multiple distinctive features that is operating on low power and lower data transfer. Code BLE Internals and Working The next thing what we need to know is a profile. Now every bluetooth device can be categorized based on certain specification which makes it easy. Here we will take a close look into two profiles of Bluetooth which is specifically designed for BLE. Generic Access Profile (GAP) - This profiles describes how two BLE devices defines discovery and establishment of connection with each other. There are two types of data payload that can be used. The Advertising Data Payload and Scan Response Payload . The GAP uses br