Skip to main content

Radare2 -commands for Reverse Engineering

 

 File and Binary Loading

  • r2 <binary>: Open a binary file.
  • r2 -d <binary>: Open a binary in debugging mode.

aaa

This is a shortcut for “analyze all." This command analyses our binary and looks for executable sections and looks for calls. when it finds a call, it looks for the destination of the call.

afl

Display all the functions in the code.

V

By pressing the capital letter V, show us all the different types of views the assembly view, graph views and the debugging view. Press the letter ‘p’ to navigate between the views.

  • pdf: Print the disassembled function where the current seek is.
  • pdr: Print function recursively (entire call graph).
  • af <address>: Analyze a specific function at <address>.
Navigation
  • s <address>: Seek to a specific address.
  • s - or s +: Move backward or forward.
  • s entry0: Seek to the program's entry point.
  • s sym.main: Seek to the main function (if symbols are present)

Disassembly and Debugging

  • pd 10: Disassemble 10 instructions from the current address.
  • px 32: Print 32 bytes in hex.
  • db <address>: Set a breakpoint at <address>.
  • dc: Continue execution.
  • ds: Step into the next instruction.
  • dso: Step over the next instruction.
  • dr: Display or modify registers (e.g., dr eax=0).

Searching

  • /c <string>: Search for a string.
  • /x <hex>: Search for a hexadecimal pattern.
  • /R <value>: Search for a specific value in memory.

Debugging in Visual Mode

  • V: Enter visual mode.
    • F2: Set a breakpoint.
    • F7: Step into.
    • F8: Step over.
    • F9: Continue execution

 Information

  • i: General information about the binary.
  • iI: Detailed imports information.
  • ii: List of imports.
  • is: List of symbols.
  • ic: List of classes (if the binary uses C++ or similar).

Comments

Popular posts from this blog

Bug Boundy Methodology, Tools & Resources

Start by defining a clear objective, such as exploiting a remote code execution (RCE) vulnerability or bypassing authentication on your target. Then, consider how you can achieve this goal using various attack vectors like XSS, SSRF, or others - these are simply tools to help you reach your objective. Use the target as how a normal user would, while browsing keep these questions in mind: 1)How does the app pass data? 2)How/where does the app talk about users? 3)Does the app have multi-tenancy or user levels? 4)Does the app have a unique threat model? 5)Has there been past security research & vulnerabilities? 6)How does the app handle XSS, CSRF, and code injection?

Install & set up mitmweb or mitmproxy in Linux

Step 1: Go to the mitmproxy page and download the binaries. Step 2: Install the downloaded tar file with the command " tar -xzf <filename>.tar.gz " Step 3: In the FoxyProxy add the proxy 127.0.0.1:8080  and turn it on. Step 4 : In the terminal run command " ./mitmweb " Step 5: Go to the page  http://mitm.it/   and download the mitmproxy's Certificate. Step 6: If you downloaded the certificate for Firefox, then go to " settings -> Privacy & Security -> Click View Certificates -> Click  Import ", then import the certificate.  Step 7: Now you are ready to capture the web traffic. Step 8 : In terminal run " ./mitmweb"

API Bug Bounty Hunting: Reconnaissance and Reverse Engineering an API

  In order to target APIs, you must first be able to find them.APIs meant for consumer use are meant to be easily discovered. Typically, the API provider will market their API to developers who want to be consumers. So, it will often be very easy to find APIs, just by using a web application as an end-user. The goal here is to find APIs to attack and this can be accomplished by discovering the API itself or the API documentation. Bug Boundy Methodology, Tools & Resources Start by defining a clear objective, such as exploiting a remote code execution (RCE) vulnerability or bypassing… adithyakrishnav.blogspot.com Reconnaissance Passive Reconnaissance It is obtaining information about a target without directly interacting with the target’s systems. Google Dorking Firstly, google search for “<app name> API”. intitle:” api” site:”google.com” inurl:”/api/v2" site:”google.com” inurl:”/api/v1" intext:”index of /” inurl:json site:”google.com” intitle:”index.of” intext:”api.t...