Skip to content

Latest commit

 

History

History
63 lines (42 loc) · 4.48 KB

bypass-payment-process.md

File metadata and controls

63 lines (42 loc) · 4.48 KB
Raw

Bypass Payment Process

{% hint style="success" %} Learn & practice AWS Hacking:HackTricks Training AWS Red Team Expert (ARTE)
Learn & practice GCP Hacking: HackTricks Training GCP Red Team Expert (GRTE)

Support HackTricks
{% endhint %}

Payment Bypass Techniques

Request Interception

During the transaction process, it is crucial to monitor the data being exchanged between the client and the server. This can be done by intercepting all requests. Within these requests, look out for parameters with significant implications, such as:

  • Success: This parameter often indicates the status of the transaction.
  • Referrer: It might point to the source from where the request originated.
  • Callback: This is typically used for redirecting the user after a transaction is completed.

URL Analysis

If you encounter a parameter that contains a URL, especially one following the pattern example.com/payment/MD5HASH, it requires closer examination. Here's a step-by-step approach:

  1. Copy the URL: Extract the URL from the parameter value.
  2. New Window Inspection: Open the copied URL in a new browser window. This action is critical for understanding the transaction's outcome.

Parameter Manipulation

  1. Change Parameter Values: Experiment by altering the values of parameters like Success, Referrer, or Callback. For instance, changing a parameter from false to true can sometimes reveal how the system handles these inputs.
  2. Remove Parameters: Try removing certain parameters altogether to see how the system reacts. Some systems might have fallbacks or default behaviors when expected parameters are missing.

Cookie Tampering

  1. Examine Cookies: Many websites store crucial information in cookies. Inspect these cookies for any data related to payment status or user authentication.
  2. Modify Cookie Values: Alter the values stored in the cookies and observe how the website's response or behavior changes.

Session Hijacking

  1. Session Tokens: If session tokens are used in the payment process, try capturing and manipulating them. This might give insights into session management vulnerabilities.

Response Tampering

  1. Intercept Responses: Use tools to intercept and analyze the responses from the server. Look for any data that might indicate a successful transaction or reveal the next steps in the payment process.
  2. Modify Responses: Attempt to modify the responses before they are processed by the browser or the application to simulate a successful transaction scenario.

{% hint style="success" %} Learn & practice AWS Hacking:HackTricks Training AWS Red Team Expert (ARTE)
Learn & practice GCP Hacking: HackTricks Training GCP Red Team Expert (GRTE)

Support HackTricks
{% endhint %}