Portswigger
  • Portswigger
  • Server-Side Request Forgery
    • Server-Side Request Forgery (SSRF)
  • SSRF with filter bypass via open redirection vulnerability
  • Blind SSRF with out-of-band detection
  • Cross-Site Scripting
    • Cross-Site Scripting (XSS)
  • Reflected XSS into a JS string with angle brackets and double&single quotes HTML-encoded escape
  • XSS into a template literal w/ angle brackets, single, double quotes, backslash & backticks Escaped
  • Authentication
    • Authentication
  • Username enumeration via subtly different responses
  • 2FA broken logic
  • Username enumeration via response timing
  • Username enumeration via account lock
  • Password reset poisoning via middleware
  • Path Traversal
    • Path Traversal
  • File path traversal, traversal sequences stripped with superfluous URL-decode
  • File path traversal, traversal sequences blocked with absolute path bypass
  • Business Logic Vulnerabilities
    • Business Logic Vulnerabilities
  • Insufficient workflow validation
  • Inconsistent handling of exceptional input
  • Server-Side Template Injection
    • Server-Side Template Injection
  • Basic server-side template injection
  • Basic server-side template injection (code context)
  • SQL Injection
    • SQL Injection
    • Blind SQL injection with conditional responses
  • SQL injection UNION attack, retrieving data from other tables
  • SQL injection attack, listing the database contents on non-Oracle databases
  • API Testing
    • API Testing
  • Exploiting an API endpoint using documentation
  • Exploiting a mass assignment vulnerability
  • Finding and exploiting an unused API endpoint
  • JWT ATTACK
    • JWT Attack
    • JWT authentication bypass via unverified signature
  • JWT authentication bypass via jku header injection
  • JWT authentication bypass via flawed signature verification
  • HTTP HOST HEADER ATTACKS
    • HTTP Host header attacks
  • Basic password reset poisoning
  • Host header authentication bypass
  • No SQL Injection
    • NoSQL Injection
  • Detecting NoSQL injection
  • Exploiting NoSQL operator injection to bypass authentication
  • Exploiting NoSQL injection to extract data
  • FILE UPLOAD VULNERABILITIES
    • File Upload Vulnerabilities
  • Web shell upload via obfuscated file extension
  • OAuth Authentication
    • OAuth Authentication
  • OAuth account hijacking via redirect_uri
  • ACCESS CONTROL VULNERABILITIES
    • Access Control Vulnerabilities
  • User ID controlled by request parameter with data leakage in redirect
  • User ID controlled by request parameter with password disclosure
  • User role controlled by request parameter
  • User role can be modified in user profile
  • URL-based access control can be circumvented
  • INFORMATION DISCLOSURE VULNERABILITIES
    • Information Disclosure Vulnerabilities
  • Information disclosure in version control history
  • XML external entity injection
    • XML External Entity (XXE) Injection
  • Exploiting XXE using external entities to retrieve files
  • Exploiting blind XXE to retrieve data via error messages
  • Blind XXE with out-of-band interaction
  • Blind XXE with out-of-band interaction via XML parameter entities
  • OS COMMAND INJECTION
    • OS Command Injection
  • Blind OS command injection with out-of-band data exfiltration
  • PROTOTYPE POLLUTION
    • Prototype Pollution
  • Privilege escalation via server-side prototype pollution
  • WEB CACHE POISONING
    • Web Cache Poisoning
  • Web cache poisoning via an unkeyed query parameter
Powered by GitBook
On this page
  1. API Testing

API Testing

API (Application Programming Interfaces) memungkinkan sistem perangkat lunak dan aplikasi untuk berkomunikasi dan berbagi data.

API Testing penting dilakukan karena kerentanan dalam API dapat merusak aspek inti confidentiality, integrity dan availability.

Semua stis web dinamis tersusun dari API, sehingga kerentanan web klasik seperti SQL injection dapat digolongkan sebagai pengujian API. Pada topik ini, akan dibahas cara menguji API yang tidak sepenuhnya digunakan oleh front-end aplikasi, dengan fokus pada API RESTful dan JSON.

Mencegah kerentanan pada API?

Saat merancang API, pastikan bahwa keamanan menjadi pertimbangan awal. Secara khusus, pastikan:

  • Amankan dokumentasi API jika tidak ingin API dapat diakses publik

  • Pastikan dokumentasi selalu update sehingga penguji yang legal memiliki visibilitas penuh terhadap attack surface API

  • Terapkan whitelist method HTTP yang diizinkan

  • Validasi bahwa jenis konten diharapkan untuk setiap request dan response

  • Gunakan error message yang umum untuk menghindari memberikan informasi yang mungkin berguna bagi penyerang

  • Gunakan tindakan pada semua versi API, bukan hanya versi production

Untuk mencegah kerentanan mass assignment, masukkan properti yang dapat diperbarui oleh pengguna ke dalam whitelist dan masukan propersi sensitif yang tidak boleh diperbarui oleh pengguna ke dalam blacklist.

PreviousSQL injection attack, listing the database contents on non-Oracle databasesNextExploiting an API endpoint using documentation

Last updated 3 months ago