Penetration Test

Introduction to XSS Attacks Cross-Site Scripting (XSS) is a prevalent web security vulnerability that allows attackers to inject malicious scripts into web pages viewed by other users. These scripts, often written in JavaScript, can steal sensitive information, manipulate website content, or impersonate users. XSS attacks exploit the trust users place in a website, leading to severe consequences for both users and web applications. Types of XSS Attacks Stored XSS (Persistent XSS)  Stored XSS occurs when malicious scripts are permanently stored on the target server, such as in a database, comment field, or forum post. When a user accesses the affected page, the script is executed in their browser. For example, an attacker might inject a script into a user profile page, which then executes whenever another user views that profile. Example CVE: CVE-2020–10385: A stored XSS vulnerability in the WPForms Contact Form plugin for WordPress. Reflected XSS  Reflected XSS happens when ma...

Introduction to SQL Injection SQL Injection (SQLi) is a prevalent attack vector that exploits vulnerabilities in web applications by manipulating SQL queries. It allows attackers to interfere with the queries an application makes to its database, potentially leading to unauthorized access to sensitive data. What is Out-of-Band SQL Injection? Out-of-Band SQL Injection (OOB SQLi) is a type of SQL injection where the attacker does not receive a response from the attacked application on the same communication channel. Instead, the application sends data to a remote endpoint controlled by the attacker. This method is particularly useful when the attacker cannot use the same channel to launch the attack and gather results. How Out-of-Band SQL Injection Works Out-of-Band SQLi relies on the ability of the database server to make DNS or HTTP requests to a remote server. The attacker injects a payload that triggers these requests, allowing them to exfiltrate data without direct interaction with ...

Introduction SQL Injection (SQLi) is a type of cyber attack that allows attackers to interfere with the queries that an application makes to its database. It is one of the most common and dangerous web application vulnerabilities. Blind SQL Injection is a subtype of SQLi where the attacker cannot see the results of the queries they inject. Instead, they infer information based on the behavior of the application. Time-based Blind SQL Injection is a specific technique where the attacker uses time delays to determine whether their injected queries are successful. Understanding Time-based Blind SQL Injection is crucial for developers and security professionals to protect applications from these attacks. This guide will provide a comprehensive overview of Time-based Blind SQL Injection, including how it works, how to identify and exploit vulnerabilities, and best practices for mitigation and prevention. What is Time-based Blind SQL Injection? Blind SQL Injection occurs when an application i...

  Introduction SQL Injection (SQLi) is a code injection technique that exploits vulnerabilities in an application's software. It allows attackers to interfere with the queries that an application makes to its database. Blind SQL Injection occurs when an attacker can infer information from the database without seeing the actual data. Boolean-based Blind SQLi relies on true/false conditions to extract information. Understanding SQL Injection SQL Injection allows attackers to execute arbitrary SQL code on a database. There are several types of SQL Injection: Classic SQL Injection : Directly retrieves data from the database. Blind SQL Injection : Infers data indirectly when the application does not display error messages or data directly. Time-based Blind SQL Injection : Uses time delays to infer information. Error-based SQL Injection : Relies on error messages to extract data. Blind SQL Injection Blind SQL Injection is used when the application does not display error messages or data ...