In this walk through, we will be going through the Application Log Injection (Add to the blog) vulnerability section from Mutillidae Labs. We will be exploring and exploiting Application Log Injection in Blog 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 has a typical blog like structure where users can add entry to the blog DB.
- I used the below statement to check if application is parsing the HTML heading tag or not and it does.
<h1> Hello </h1>
- I used the below payload to exploit the vulnerability in the application and got a pop up alert.
<img src=x onerror=alert("Hacked")>;
Also Read: Mutillidae – SQLi: Extract Data (User Lookup)
Conclusion:
So, we finally completed all the security levels for the Mutillidae Application Log Injection (Add to the blog) 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”.
