Google(Apigee.com) ClickJacking Vulnerability

-
Hi folks, 

 This post is about one of my recent finding in apigee.com which was acquire by google in 2016. So i was monitoring request and responses, i noticed the following endpoint which has X-frame-options response header missing as shown in the below image.

 https://apigee.com/platform/<orgnization_name>/users/<user_email>

So i quickly visited the page and there is a option to remove the user as shown in the below image.

In this case if the attacker is inside the origination he can easily trick the administrator to remove other users. 

Working POC:

                                

 Response from the google

Sad story :p 
Thanks for reading ;) 

Comments

Post a Comment

Popular posts from this blog

How I bypassed 2-Factor Authentication in a bug bounty program

-
Image
Hello readers, This post is about one of my recent finding in a private bug bounty program on hackerone. For the sake of privacy, let’s call the site as bountyplease.com According to Bountyplease.com scope, they are more interested in Authentication related issues. So I decided to test their 2-Factor Authentication mechanism. As normal 2-Factor Authentication flow the process works in the following steps. 1. User login to account by providing valid email and password 2. A valid OTP send to users register number 3. User fill OTP 4. Login successful But in case if any user lose their phone or SIM card the process works in the following steps. 1. User login to account by providing valid email and password 2. User select other options 3. User provide backup codes 4. Login successful In both above described cases there is also a code flow as following. 1. User login to account by providing valid email and password 2. At this stage bountyplease.com display a pa...
Read more

Story of a JSON XSS

-
Image
Hi folks, This post is about of one of my recent my finding in a bug bounty program. I started checking the application for common vulnerabilities but got nothing after spending an hour I came across an endpoint which looks as follows. If you look at request and response you will see the value of status parameter is reflecting back in the response. So I tried replacing the value of status parameter and same reflected back in the response as shown in below. What next? Let’s check for XSS with a simple payload as shown in below. But angle brackets getting filtered, after I tried some encodings but nothing worked. So I was about to give up but suddenly i decided to try array tricks. So you can see whatever we write inside the round brackets is reflecting back in response as it becomes associated array as follows Status    Equals JSON object <haha> Equals Key of JSON o...
Read more