AppSecExplained
  • Index < START HERE
    • My courses
    • How to get started from zero
  • 📽️Live Stream Content
    • Resource of the week
  • Discovery / Recon
    • Methodology
    • Content discovery / recon
      • Subdomains
      • Endpoints
      • Parameters
      • Spidering
  • Common vulns
    • SQL injection overview
      • Detection
      • Blind SQLi
      • Second-order SQLi
      • SQLi lab setup & writeups
    • NoSQL injection
    • JavaScript injection (XSS)
      • XSS Methodology
    • File Inclusion
      • Local file inclusion
        • Directory traversal
    • Command injection
    • XXE (XML external entity) injection
      • Blind XXE
    • Template injection
      • Server-side template injection
      • Client-side template injection
    • Authentication
      • Attacking password-based authentication
      • Attacking MFA
      • Authentication lab setup & writeups
    • Cross-Site Request Forgery (CSRF)
    • Insecure deserialization
      • PHP
      • Java
      • Python
      • .NET
    • Server-side request forgery (SSRF)
    • Insecure file upload
    • Clickjacking
    • Open redirect
    • Vulnerable components
    • Race conditions
      • Limit overrun
    • Prototype pollution
      • Client-side prototype pollution
    • APIs
      • API: BOLA
      • API: Broken authentication
      • BOPLA
      • API: BFLA
  • Bypassing controls
    • Rate limiting
    • WAF Bypasses
  • Scripts
    • Docker-compose.yml files
      • Wordpress
      • SQLi testing labs
    • PHP scripts
      • RCE Function Check
    • Wordlists
      • Single characters
      • SQLi
  • Code review
    • Getting started
    • Sinks
  • Links worth your time
    • Practical API Hacking
    • Rana Khalil's Web Security Academy Course
    • Portswigger's Web Security Academy
    • TCM Security Discord
    • PentesterLand Writeups
Powered by GitBook
On this page
  • Blind SQL Injection
  • Other learning resources:
  • Writeups:
  • Checklist:

Was this helpful?

  1. Common vulns
  2. SQL injection overview

Blind SQLi

Blind SQL Injection

Blind SQL injection (Blind SQLi) is a type of SQL injection attack where the attacker can exploit the database, but the application does not display the output. Instead, the attacker must "infer" data by sending payloads and observing the application's behavior or responses.

A simple example:

  • A vulnearble webapp uses an API for its search to return the number of results found.

  • A user searches for a product, and the application returns with "X products found" without displaying product details.

  • The application uses the SQL query SELECT COUNT(*) FROM products WHERE product_name LIKE '%{searchTerm}%'.

  • An attacker could exploit this by injecting SQL conditions into the {searchTerm}.

  • For exmaple, searching for laptop' AND 1=1-- - returns "1 product found" and searching for laptop' AND 1=2-- - returns "0 products found", this behavior can be an indicator of a potential Blind SQLi vulnerability.

Blind SQLi is more time-consuming than regular SQLi but is just as dangerous. It can lead to:

  • Sensitive data exposure

  • Data manipulation

  • Authentication bypass

  • Potential discovery of hidden data

Other learning resources:

  • OWASP: https://owasp.org/www-community/attacks/Blind_SQL_Injection

  • SQLmap's guide on Blind SQLi: http://sqlmap.org/

  • PenTestMonkey's Cheat Sheet: http://pentestmonkey.net/cheat-sheet/sql-injection/mysql-sql-injection-cheat-sheet

Writeups:

Checklist:

PreviousDetectionNextSecond-order SQLi

Last updated 1 year ago

Was this helpful?