In this walk through, we will be going through the Cross Site Scripting Reflected (Custom Headers) vulnerability section from bWAPP Labs. We will be exploring and exploiting Reflected Cross Scripting vulnerability in Custom Headers 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: Low
- Setting the security level to Low.
- The application page can use custom HTTP headers request. It has also provided a hint for the allowed customer header – bWAPP.
- I intercepted the request and add our customer header along with the below payload. On forwarding the request, i received a pop-up alert.
bWAPP: <script>alert("Hacked")</script>
Security: Medium
- Setting the security level to Medium.
- I intercepted the request via Burpsuite and added our customer header with the below payload. On forwarding the request, it gives us the pop-alert.
bWAPP: <script>alert(1)</script>
- Not working in hard level.
Also Read: bWAPP – Cross Site Scripting Reflected (JSON)
Conclusion:
So, we finally completed all the security levels for the bWAPP Cross Site Scripting Reflected (Custom Headers) 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. Reflected-XSS attacks can be mitigated by performing input sanitization on endpoints, whitelist the allowed characters in the input and using a WAF. On that note, i will take your leave and will meet you in next one with another bWAPP vulnerability writeup, till then “Keep Hacking”.
