Security Blog

                          Do not trust client-side data challenge  Hi Guys,     A few days ago, I hosted a small PHP based Remote code execution challenge. Chall Page. I was using one of the dangerous PHP function eval() inside the code which was taking input directly from User-Agent Header and reflecting back to the challenge page. Also, there was one GET parameter "name" which was taking text from the user and reflecting back to the home challenge page. name parameter was for distraction only. The actual injection point was the User-Agent header. So lets first see what PHP documentation says about Eval() function. https://www.php.net/manual/en/function.eval.php Caution :  "Pay special attention not to pass any user-provided data into it without properly validating it beforehand"                                                             Else you know 😂 Solution : Solution.  Payload : <?php system('ls')

                         Stealing local storage data through XSS In this blog, I'm going to show how to steal local storage data and one of my same finding on bugcrowd.😀 See screen shot below which is storing sensitive data in Local Storage. Local Storage. Its easy to steal this Local stored data through javascript localStorage.getItem() function. lets alert this data through console for demonstration. Payload : alert(localStorage.getItem('access_token')) Simple Example through Console  I have found same challenge previously on bugcrowd private program.  Authorisation token was responsible to handle web application session but they are storing that authorisation token in local storage. which is not a good way to protect session tokens.  So i manged to find Stored XSS on that program and that XSS is getting executed on Admin Account. Bingo !! 😜 it take me 2 min to craft payload and steal that authorisation token. ezpz 😎

OLX Reflected XSS on Resend Code link !!  This is my first write up ! sharing is caring !!  😎         This is not big finding , just one of my noob xss that i have found on OLX.in To change password , OLX firstly sends OTP to registered phone number and hold on for user to enter OTP number but on the same page they have provided the link which resend code (which get highlight after some seconds if user failed to enter the code) so i checked the request and response of that resend code functionality and its pretty sending mobile number and hash as parameter ph="phone number" & h="hash" I changed that default user "ph" value to victims number but no luck because of another parameter "h=xxxxxxxxxxxxxxxxxxxx" (hash) 😫 So after that i decided to test for XSS  on same functionality and found one ! ✌😜 OLX Reflected XSS I checked the context and entered payload in "ph" parameter ph= " onmouseover="alert