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. XML external entity injection

XML External Entity (XXE) Injection

XML external entity injection (XXE) merupakan kerentanan keamanan aplikasi web yang memungkinkan penyerang mengganggu pemrosesan data XML oleh aplikasi.

Sering kali, penyerang dapat melihat file pada filesystem aplikasi dan berinteraksi dengan sistem backend atau eksternal yang dapat diakses oleh aplikasi itu sendiri.

Dalam beberapa situasi, penyerang dapat meningkatkan serangan XXE untuk membahayakan server yang mendasarinya atau infrastruktur backend lainnya, dengan memanfaatkan kerentanan XXE untuk melakukan serangan server-side request forgery (SSRF).

Jenis-jenis XXE:

  • Exploiting XXE to retrieve files Dimana external entity didefinisikan yang berisi konten file dan dikembalikan dalam response aplikasi

  • Exploiting XXE to perform SSRF attacks Dimana external entity didefinisikan berdasarkan URL ke sistem backend

  • Exploiting blind XXE exfiltrate data out-of-band Dimana data sensitif dikirim dari server aplikasi ke sistem yang dikendalikan oleh penyerang

  • Exploiting blind XXE to retrieve data via error messages Dimana penyerang dapat memicu error messages penguraian yang berisi data sensitif

Cara mengatasi kerentanan XXE?

Hampir semua kerentanan XXE muncul karena library parsing XML aplikasi mendukung fitur XML yang berpotensi berbahaya yang tidak dibutuhkan atau tidak ingin digunakan oleh aplikasi. Cara termudah dan paling efektif untuk mencegah serangan XXE yaitu dengan menonaktifkan fitur tersebut.

Secara umum, menonaktifkan resolusi exernal entities dan menonaktifkan dukungan untuk XInclude sudah cukup. Hal ini biasanya dapat dilakukan melalui opsi konfigurasi atau dengan mengganti perilaku default secara terprogram. Lihat dokumentasi untuk library parsing XML atau API untuk detail cara menonaktifkan kapabilitas yang tidak diperlukan.

PreviousInformation disclosure in version control historyNextExploiting XXE using external entities to retrieve files

Last updated 3 months ago