AWS S3 keys Leak
WordPress configuration file (wp-config.php) leaked, exposing AWS S3 keys and sensitive database credentials.
Security Misconfiguration (SM)
How this template works
The template uses API selection filters to specify the response code range (between 200 and 299) and to extract the URL from the response using the "urlVar" variable.
The template executes a single request by modifying the URL with the paths specified in the "urlPaths" word list. This allows the template to check for the presence of specific files, such as "wp-config.php-backup" and "%c0", in the URL.
The template validates the response payload by checking if it contains specific keywords, such as "access-key-id", "secret-access-key", "DB_NAME", and "DB_PASSWORD". If any of these keywords are found in the response, it indicates a potential leak of AWS S3 keys and sensitive database credentials.
Frequently asked questions
What is the purpose of this test
How does the test identify the presence of the wp-config.php file
What are the potential impacts of exposing AWS S3 keys and database credentials
What category and severity level does this test assign to the identified vulnerability
Are there any references or resources available for further understanding of S3 leaks
How does the test validate the presence of sensitive information in the response payload