Http Sensitive File Exposed

Description

This detector identifies exposed sensitive files on web servers that should not be publicly accessible. It attempts to access common sensitive file paths (like configuration files, backups, logs, or development files) and validates if the responses contain actual sensitive content rather than just error pages.

Weakness:

362 - Technical information leak - Content response

Category: Unexpected Injection

Detection Strategy

    Attempts to access a predefined list of sensitive file paths by making HTTP requests to these URLs

    Only reports vulnerabilities when the HTTP response returns a 200 status code (successful access)

    Validates that the response content actually contains sensitive information using specific content validators for each file type

    Creates vulnerability reports for each successfully accessed sensitive file that contains valid sensitive content