Skip to content

Payloads Module

Munir Njiru edited this page Nov 24, 2015 · 2 revisions

#Payloads Module This module is intended to store items that you frequently use . Assuming you are in an internal pentest and you have no access to the internet , there are those common payloads you use contextually but can't seem to find them , instead of having them in several notepads that are hard to find when you most need them you can have them centrally and build your mini repository.

Most of these payloads are usually in relation to input injection or URL manipulation. However if others are also there they can be others outside this and this we categorize as miscellaneous. Currently the categories set are:

  • SQL Injection
  • HTML Injection
  • Cross Site Scripting
  • Local File Inclusion
  • Miscellaneous

These can be added in the backend but viewing can be done without logging into the framework via the frontend.

The form contains 5 fields:

  • Name - This holds a simple descriptive title for the exploit that you can remember fast.
  • Type - This shows the type of attack it is e.g. is it an SQL Injection or LFI or XSS etc
  • Category - This gives a more detailed breakdown of what type of attack it is e.g. if stated to be SQL Injection is it error based, Blind, Time Based etc or is it for MSSQL ,MySQL, PostgreSQL or oracle; Another example would be like XSS is it reflected, DOM Based or stored.
  • Payload - The actual payload string that you would use to test the attack.
  • Description - Detailed description of what the attack does and how to use it , additionally if there are alternative methods of performing the attack they would be described at this point.

#Adding A payload To add a payload follow the steps below :

  • Click on Payloads in the backend.
  • Click on New Payload
  • Fill in the relevant details, this is explained further below.

Based on the understanding above lets use a sample of the Zimbra Collaboration Server LFI . This affects a number of versions but one key thing to note it can be done via two methods i.e. the Frontend or the backend admin service , we only have one payload instance instead of duplicating we can lay it out as below:

Adding a Payload

#Viewing the Payload After adding it in the backend we can be referring to it from the front end by clicking view against its title , it will appear on the first page as it is the latest addition.

Adding a Payload

This module can come quite in handy when you need your own repository and notes about attacks you do so that you have a quick reference anywhere, anytime.