Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 70 views

    03 Burp Match and Replace

    Uploaded by

    Bagong
    This document discusses using Burp Suite's "Match and replace" option to automate testing. It describes setting up rules to automatically replace authorization headers to test for IDOR, and to replace CSRF tokens in requests to test for CSRF vulnerabilities. The document encourages thinking creatively about all the possible values that could be changed in requests and responses to find vulnerabilities.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    03 Burp Match and Replace

    Uploaded by

    Bagong
    70 views5 pages
    This document discusses using Burp Suite's "Match and replace" option to automate testing. It describes setting up rules to automatically replace authorization headers to test for IDOR, and to replace CSRF tokens in requests to test for CSRF vulnerabilities. The document encourages thinking creatively about all the possible values that could be changed in requests and responses to find vulnerabilities.

    Original Title

    03_Burp_Match_and_replace

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document discusses using Burp Suite's "Match and replace" option to automate testing. It describes setting up rules to automatically replace authorization headers to test for IDOR, and to replace CSRF tokens in requests to test for CSRF vulnerabilities. The document encourages thinking creatively about all the possible values that could be changed in requests and responses to find vulnerabilities.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    70 views5 pages

    03 Burp Match and Replace

    Uploaded by

    Bagong
    This document discusses using Burp Suite's "Match and replace" option to automate testing. It describes setting up rules to automatically replace authorization headers to test for IDOR, and to replace CSRF tokens in requests to test for CSRF vulnerabilities. The document encourages thinking creatively about all the possible values that could be changed in requests and responses to find vulnerabilities.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 5

    🤖

    Burp: Match and replace


    Introduction
    Replacing authorization headers
    Automatically replacing CSRF tokens
    The sky is the limit

    Introduction
    Burp suite's proxy options have an option called "Match and replace" available.
    This option has many rich uses that can help us automate our testing process.
    With some smart uses of this amazing option, we can automatically test for CSRF,
    IDOR, command injection,.. by just clicking around in the application! Let's explore
    this magical tool and it's many options.

    Replacing authorization headers


    Since authorize basically just matches the authorization headers and attempts to
    replace them with the ones the user supplied, we can set up a similar rule in the
    proxy.

    Burp: Match and replace 1


     Usually the request header will contain the authorization methods

     Fill in the tokens of the logged in user

     Fill in the tokens of a second user you want to use

    Now, as long as this rule is active you can click around in the application. If you
    can open any information that should not be public, we have an IDOR on our
    hands.
    To disable this rule, simple uncheck the checkbox in front of it.

    Automatically replacing CSRF tokens

    Burp: Match and replace 2


    Depending on if the CSRF token is in the HEADER or the BODY section of the
    request, we will need to pick one.

    Burp: Match and replace 3


    Fill in the regex to indicate to burp how it can find the CSRF token in your request
    and replace it with a value of your own. Be careful, this is just an example, it may
    be different for your target.

    Burp: Match and replace 4


    When this rule is active, click through the application and try to make changes. If
    you are able to make changes where a CSRF token is normally expected,
    investigate this further. It may be a vulnerability. To restore normal functionality,
    simply disable this rule.

    The sky is the limit


    You can change any value you want in either

    The response

    The request

    And in either

    The header

    The body

    Request Parameter names

    Request Parameter values

    Request first line

    These give us an infinte amount of possibilites so the sky is the limit... Think
    outside the box!

    Burp: Match and replace 5

    You might also like