Security Notes
  • Whoami
  • Pentesting
    • WEP-Pen
      • Reconnaissance
      • Enumeration
      • OWSAP TOP 10
        • Injection
          • Cross Site Scripting
            • Cross Site Scripting
            • Exploitation
            • Protections
          • SQL Injection
            • SQL Injection Overview
          • NoSQL Injection
          • CRLF Injection
          • XML Injection
        • Broken Access Control
          • Path Traversal
          • Sensitive Cookie with Improper SameSite Attribute
          • Link Following
          • Incorrect Default Permissions
          • Information disclosure
          • CSRF
            • csrf checklist
          • 403 bypass
          • Exposure of WSDL File Containing Sensitive Information
          • bussiness logic checklist
          • 2FA bypass checklist
          • admin panal checklist
          • idor checklist
          • Authentication checklist
          • reset_password_checklist
          • ATO
        • Cryptographic Failures
          • Cryptographic Failure
          • Weak Encoding for Password
          • Improper Following of a Certificate's Chain of Trust
            • Understanding Digital Certificates : Self-Signed and CA-Signed Certificate **
            • Transport Layer Security (TLS) and SSL **
          • Clear Text Transmission Of Sensitive Data
            • SSLStripping **
        • Insecure Design
        • Security Misconfiguration
          • CORS Miscofigration
          • Mail Server Misconfiguration
        • Vulnerable and Outdated Components
          • Using Components with Known Vulnerabilities
        • Identification and Authentication Failures
          • JWT Hacking
          • SAML Authentication bypass
        • Software and Data Integrity Failures
          • mass assignment
          • PostMessage Vulnerabilities
            • PostMessage Vulnerabilities
            • Blocking main page to steal postmessage
            • Bypassing SOP with Iframes - part 1
            • Bypassing SOP with Iframes - part 2
            • Steal postmessage modifying iframe location
        • Security Logging and Monitoring Failures
        • Server-Side Request Forgery (SSRF)
          • SSRF
      • Checklists
        • aem misconfiguration
        • exif_geo
        • xss
        • Session Management
        • Authorization
        • cookie
        • Django
        • Symfony
        • json
        • bypass rate limit
        • Rce
        • Register Page
      • eWPTXv2 Preparation
        • Encoding & Filtering
        • Evasion Basics
        • Cross-site scripting (XSS)
        • XSS Filter Evasion
        • Cross-site request forgery (CSRF
        • HTML5
      • API-Pen
        • API Discovry
        • Reverse Engineering API Documentation
        • Excessive Data Exposure
        • Vulnerability Scanning
        • API Authentication Attacks
          • Classic Authentication Attacks
          • API Token Attacks
        • API Authorization Attacks
          • Broken Object Level Authorization (BOLA)
          • Broken Function Level Authorization
        • Improper Assets Management
        • Mass Assignment
        • SSRF
        • Injection Attacks in API
        • Evasive Maneuvers
        • GraphQL Vulnerabilities
    • NET-Pen
      • Active Directory Pentesting
        • Active Directory Components
        • Initial Attack Vectors
          • LLMNR Poisoning
          • SMB Relay Attacks
          • IPv6 Attacks ( IPv6 DNS Takeover )
          • Printer Hacking
          • Methodology
          • Some Other Attacks
            • Zerologon (CVE-2020-1472)
            • PrintNightmare (CVE-2021-1675)
        • Post-Compromise Attacks
          • Pass Attacks
          • Kerberoasting Attack
          • Token Impersonation Attack
          • LNK File Attack
          • GPP / cPassword Attacks
          • Mimikatz
          • Methodology
        • We've Compromised the Domain
          • Dumping the NTDS.dit
          • Golden Ticket Attacks
          • Methodology
        • Case Study
        • Password Attacks
      • Attack Vectors by Port
        • FTP 21
        • SSH 22
        • Telnet 23 - 2323
        • SMTP 25
        • DNS 53
        • Kerberos 88
        • POP 110-995
        • RPC 111
        • Ident 113
        • NNTP 119
        • NetBIOS 137-138
        • SMB / Samba 135-139, 445
        • MSRPC 135
        • SNMP 161
        • LDAP 389,636
        • Modbus 502
        • OpenSSL 1337
        • Ms-SQL 1433
        • Oracle Listener 1521 1522 1529
        • NFS 2049
        • MySql 3306
        • RDP 3389
        • ADB Android Debug Bridge 5555
        • WinRM 5985 5986
        • VNC 5800 5900
        • Redis 6379
        • Unreal IRC 6667
        • Tomcat 8080
        • MongoDB 27017
        • http 80
      • Network basics
      • Information Gathering
      • Privilege Escalation
        • Windows Privilege Escalation
        • Linux Privilege Escalation
    • write-ups
      • How i found a Privilege Escalation via Impersonation Features feature
      • How I was able to discover ATO Via IDOR vulnerability
      • Easy full Account Takeover via Facebook OAuth Misconfiguration
Powered by GitBook
On this page
  • How to test for information disclosure vulnerabilities:
  • #Lab-1:Information disclosure in error messages.
  1. Pentesting
  2. WEP-Pen
  3. OWSAP TOP 10
  4. Broken Access Control

Information disclosure

PreviousIncorrect Default PermissionsNextCSRF

Last updated 2 months ago

Information disclosure: Information disclosure, also known as information leakage, is when a website unintentionally reveals sensitive information to its users.

How to test for information disclosure vulnerabilities:

Check for information disclosure:

  1. robots.txt

  2. Source code,path analysis

  3. Default file(phpinfo,login,admin,.git)

  4. method check(GET,PUT,TRACE,POST,OPTIONS)

Basic Example of IDV:

1.Revealing the names of hidden directories, their structure, and their contents via a robots.txt file or directory listing. 2.Providing access to source code files via temporary backups. 3.Explicitly mentioning database table or column names in error messages. 4.Unnecessarily exposing highly sensitive information, such as credit card details. 5.Had-coding API keys, IP addresses, database credentials , and so on in the source code. 6.Hinting at the existence or absence of resources, usernames, and so on via subtle differences in application behaviour.

How do IDV arise:

1.Failure to remove internal content from public content. 2.Insecure configuration of the website and related technologies. 3.Flawed design and behaviour of the application.

.

Tools: Burpsuite

Description: This lab’s verbose error messages reveal that it is using a vulnerable version of a third-party framework. To solve the lab, obtain and submit the version number of this framework.

Firstly access the lab and intercept the burpsuite.After intercept the burpsuite we change the product id.

GET /product?productId=1 HTTP/2

Instead of number we used strings and repeater mode.Then send the request.The response was internal server error .

GET /product?productId=”nishad” HTTP/2

after change the parameter it shows the server version 2.2.3.31

Description: This lab contains a debug page that discloses sensitive information about the application. To solve the lab, obtain and submit the SECRET_KEY environment variable.

Tools: Burpsuite

To automate hunting for comments, you can use Burp:

  1. Navigate to Target and select Site Map.

  2. Right click the correct target, select Engagement Tools, and select Find Comments.

/cgi-bin/phpinfo.php

Then send the request in repeater & the response was ok.The secret key was lthjb1r4llnrlvflycxxb0v3ieivwjgg.

Description: This lab leaks its source code via backup files in a hidden directory. To solve the lab, identify and submit the database password, which is hard-coded in the leaked source code.

Firstly check the robots.txt file and see the /backup file is disallow.Then check /backup file the source code are visible and password was given.The password was : oifs3ta0y6fkjk8d2ql5k2l7wp0ywk7h

Then submit the password the lab is solved.

Description: This lab’s administration interface has an authentication bypass vulnerability, but it is impractical to exploit without knowledge of a custom HTTP header used by the front-end.

To solve the lab, obtain the header name then use it to bypass the lab’s authentication. Access the admin interface and delete the user carlos.

You can log in to your own account using the following credentials: wiener:peter

Firstly login username:wiener & password:peter and intercept the burpsuite.

GET /product?productId=2 HTTP/2 check the method.Apply TRACE method and used “/admin”

TRACE /admin HTTP/2

TRACE method used for only debugging.After that it shows

X-Custom-IP-Authorization: 103.118.78.140 & expose the critical information.

After change the TRACE method we used GET method.GET method show only data.Then we send the data in the browser.

Solve the lab.congratulations

Description: This lab discloses sensitive information via its version control history. To solve the lab, obtain the password for the administrator user then log in and delete the user carlos.

#Lab-2 : .

.

#Lab-4 : .

#Lab-4 : .

wget -r

1.Fuzzing
2.Using Burp Scanner
3.Using Burp’s engagement tools
4.Engineering informative responses
#Lab-1:Information disclosure in error messages
Information disclosure on debug page
#Lab-3 : Source code disclosure via backup files
Authentication bypass via information disclosure
Information disclosure in version control history
https://0a1c009704343dd680b63055008500fe.web-security-academy.net/.git