eCPPTv2-PTP-Notes
HomeGitHubPortfolioTwitter/XMediumCont@ct
  • 📝eCPPTv2 / PTP - Notes
  • 1️⃣1 - ​System Security
    • 1.1 Architecture Foundamentals
    • 1.2 Assemblers and Tools
    • 1.3 Buffer Overflow
    • 1.4 Cryptography
    • 1.5 Malware
    • 1.6 Shellcoding
  • 2️⃣2 - Network Security
    • 2.1 System/Host Based Attacks
      • 2.1.1 Windows Vulnerabilities
    • 2.2 Network Based Attacks
    • 2.3 The Metasploit Framework (MSF)
      • MSF Introduction
      • Information Gathering & Enumeration
      • Vulnerability Scanning
      • Client-Side Attacks
      • Post Exploitation
      • Armitage
    • 2.4 Exploitation
    • 2.5 - Post Expolitation / Pivoting
      • 2.5.1 Pivoting Guidelines
      • 2.5.2 Pivoting Example (3 Targets)
    • 2.6 Social Engineering
  • 3️⃣3 - PowerShell for PT
    • 3.1 PowerShell
  • 4️⃣4 - Linux Exploitation
    • 4.1 Linux Vulnerabilities
    • 4.2 Linux Exploitation
    • 4.3 Linux Post-Exploitation
    • 4.4 Linux Privilege Escalation
      • 4.4.1 Kernel Exploitation
      • 4.4.2 SUID Exploitation
      • 4.4.3 CronJobs
  • 5️⃣5 - Web App Security
    • 5.1 - Web App Concepts
      • 5.1.1 HTTP/S Protocol
      • 5.1.2 Encoding
      • 5.1.3 Same Origin
      • 5.1.4 Cookies
      • 5.1.5 Session
      • 5.1.6 Web App Proxies
    • 5.2 - Information Gathering
      • 5.2.1 Gathering Information on Your Targets
      • 5.2.2 Infrastructure
      • 5.2.3 Fingerprinting Frameworks and Applications
      • 5.2.4 Fingerprinting Custom Applications
      • 5.2.5 Enumerating Resources
      • 5.2.6 Information Disclosure Through Misconfiguration
      • 5.2.7 Google Hacking
      • 5.2.8 Shodan HQ
    • 5.3 - Cross Site Scripting
      • 5.3.1 XSS Anatomy
      • 5.3.2 Reflected XSS
      • 5.3.3 Stored XSS
      • 5.3.4 DOM-Based XSS
      • 5.3.5 Identifying & Exploiting XSS with XSSer
    • 5.4 - SQL Injection
      • 5.4.1 Introduction to SQL Injection
      • 5.4.2 Finding SQL Injection
      • 5.4.3 Exploiting In-Band SQL Injection
      • 5.4.4 Exploiting Error-Based SQL Injection
      • 5.4.5 Exploiting Blind SQL Injection
      • 5.4.6 SQLMap
      • 5.4.7 Mitigation Strategies
      • 5.4.8 From SQLi to Server Takeover
    • 5.5 - Other Common Web Attacks
      • 5.5.1 Session Attacks
      • 5.5.2 CSRF
  • 6️⃣6 - ​Wi-Fi Security
    • 6.1 Traffic Analysis
  • 7️⃣7 - ​Metasploit & Ruby
    • 7.1 Metasploit
  • 📄Report
    • How to write a PT Report
  • 🛣️RoadMap & My Experience
  • 📔eCPPT Cheat Sheet
Powered by GitBook
On this page
  • Fingerprinting Frameworks and Applications
  • Fingerprinting Web Applications
  • Fingerprinting Third-Party Add-Ons
  1. 5 - Web App Security
  2. 5.2 - Information Gathering

5.2.3 Fingerprinting Frameworks and Applications

Fingerprinting Frameworks and Applications

After obtaining a list of subdomains, the next step involves identifying the frameworks and applications running on each subdomain. This information is crucial for understanding potential vulnerabilities.

Common Applications

Common applications, whether open source or commercial, are interesting for analysis due to their source code accessibility. Unlike in-house applications, testers can review both the application logic and implemented security controls. Some common applications include forums (e.g., phpBB, vBulletin), Content Management Systems (CMS) like Joomla or Drupal, Customer Relationship Management (CRM) systems, blogging platforms (e.g., WordPress, Movable Types), and social networking scripts.

Fingerprinting Web Applications

Identifying the exact application and version is essential for finding publicly available exploits. Techniques include:

  • Browsing the Website:

    • Look at URLs, appearance, and logic of webpages.

    • Search for the application's name in page content.

    • Inspect web page source; the name and version might be in HTML comments or HTTP headers.

  • Sending a GET Request:

    • Examine response headers for information.

    • Example (Joomla):

      plaintextCopy codeRequest:
      GET / HTTP/1.1
      Host: www.joomla.org
      User-Agent: Mozilla/5.0 (x11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Iceweasel/31.5.3
      
      Response:
      HTTP/1.x 200 OK
      Content-Encoding: gzip
      Content-Type: text/html; charset=utf-8
      Server: LiteSpeed
      Vary: Accept-Encoding
      X-Content-Encoded-By: Joomla! 2.5

      Here, the server is running Joomla! 2.5.

  • Footer Notifications:

    • Some applications require users to keep a footer notification for support and acknowledgment.

    • Example (vBulletin):

      plaintextCopy codeCopyright © 2015 vBulletin Solutions. All Rights Reserved
      vBulletin® is a registered trademark of vBulletin Solutions.
  • Source Code Examination:

    • Examine web page source code for information in META tags and HTML comments.

    • Example (WordPress):

      htmlCopy code<meta name="generator" content="Wordpress 4.2-beta-31946" />

Fingerprinting Third-Party Add-Ons

Common CMS platforms like Joomla, Drupal, and Mambo often have large support communities providing free add-ons, components, and extensions. These third-party add-ons can introduce vulnerabilities. Fingerprinting installed add-ons can involve examining website URLs, as these URLs typically consist of three main parts:

plaintextCopy codeindex.php?option=%component_name%&task=%task_value%

In Joomla, for example, the option parameter in the URL reveals installed third-party add-ons. For instance:

plaintextCopy codeindex.php?option=com_docman&task=doc_view&gid=100

This URL indicates the use of the Docman document manager component.

In the information-gathering process, it is crucial not only to list common applications in use but also to identify third-party add-ons, potentially useful for penetration testing tasks.

Previous5.2.2 InfrastructureNext5.2.4 Fingerprinting Custom Applications

Last updated 1 year ago

5️⃣