In this walk through, we will be going through the Application Log Injection (Captured Data) vulnerability section from Mutillidae Labs. We will be exploring and exploiting Application Log Injection in Captured Data implementations and learn how application are affected because of it. So, let’s get started with the Hacking without any delay.

Table of Contents
Security Level: 0 (Hosed)
- Setting the security level to 0 or Hosed.

- The application shows the captured data from the captured-data.php page. The designated page captures the useragent and other HTTP header information and displays on page.


- I intercepted the request and change the showhints parameter in the cookie value to the below payload and it worked.
<script>alert(1)</script>



- I used the below payload to store the payload value in the DB and whenever the user tries to view the captured data, payload will be executed automatically.
<img src=x onerror=alert("Hacked")>


Also Read: Mutillidae – Sensitive Data Exposure
Conclusion:

So, we finally completed all the security levels for the Mutillidae Application Log Injection (Captured Data) Vulnerability. We looked into the various ways how application has been set up in various levels and how we can bypass the security controls implemented. Next, we can mitigate the potential Application Log Injection attacks by performing input sanitization on endpoints, whitelist the allowed characters in the input and using a WAF. Along with that, we can prevent data from any untrusted source to be dynamically written to the HTML document. On that note, i will take your leave and will meet you in next one with another Mutillidae vulnerability writeup, till then “Keep Hacking”.