Skip to main content

Facebook Pixel analytics was still visible to the user who was removed from permissions (Fixed)

Bug discovered on :3rd February, 2018 
You can read about Facebook Pixel here : https://developers.facebook.com/docs/facebook-pixel
User 'A' and User 'B' are having their own accounts in Facebook Business ( business.facebook.com )
User 'A' - Victim          User 'B'- Attacker
User 'A' creates  Facebook Pixel.

Earn more by display ads on blog with Lithific Ads
'A' assigns User 'B' as a Pixel Analyst using B's Business ID.
Want to get icons for app Development Here  it's 


User 'B' creates an Event Source Group and Chooses A's pixel in it
User 'B' visits his Event source group he created and opens the settings page. A's pixel analytics can be accessed from this page.

This is how the Pixel's analytics page looks like. Since this is a new pixel the data is not available.

User 'A' now removes the permissions given to User 'B'.


User 'B' visits the analytics page of the Pixel. The Analytics data will be still accessible though he doesn't have any permissions.

After the mitigation of the flaw....
Now if the person who doesn't have any permissions visits the analytics page he would be displayed this page.


3rd February, 2018 - Bug reported
10th February, 2018 - Report was sent to product team (Triaged).
24th February , 2018 - Reply from Facebook that the bug was fixed.
14th March, 2018 - Bounty of $750 awarded. My first bounty from Facebook!!

Earn more by display ads on blog with Lithific Ads

Comments

Post a Comment

Popular posts from this blog

$1337 YouTube Community (Posts) bug

YouTube Community  is a feature that is only available for Channels with  1. Verified Phone numbers 2.  A significant history, more content for years. In the early June I started hunting for Security flaws on YouTube I was roaming around the features but most of the places have been found secure or already potential features had the bugs fixes in place. The Community Tab is now Posts So, I thought to exploit Youtube Community feature. I was trying to delete the Posts using IDOR attacks but it didn't work I was tired of trying various attacks but thought to compromise to the least "Privilege escalation".  The Security flaw... A user (victim) created a YT Community post, later an attacker while being an Admin of the same Channel has saved the HTTP Request that deletes a Community Post / Poll, then the attacker can replay that HTTP Request after he's demoted from Admin to Subtitle Editor  that would delete the Post / Poll. I exploited this flaw I tried after 15 ...
Post a Comment
Read more

Facebook Bug Bounty $$$$ : Crossposting Live Videos | Facebook Live

In the Facebook Page Settings, you could setup the option for Crossposting Live videos from other pages.  The Attacker's page adds a Page (Victim's Page) for crossposting their videos Victim Page's Admin accepts the approval and the default option is Crossposting videos without further approval The Attacker starts live video and selects Victim's Page in the "Crosspost to more pages" Victim visits the Crossposting page in the Page settings and and removes Attacker's Page Attacker selects "Use camera" and clicks on "Go Live". The Victim's Page starts automatically crossposting the live video of Attacker,  Bug Bounty of $500
Post a Comment
Read more

Instagram Reels bug $$$$ Bug Bounty : Making users share unintented reels

 This bug is categorised as IDOR. We all share Instagram reels with our friend via DM.  Did you every try "Copy link" and share on mediums like WhatsApp or any similar apps ?  When you do that, the generated Link would be of the below URL https://www.instagram.com/reels/<REEL_ID>?igsh=<Encrypted> The igsh in the Query params of URL is an encrypted string, that would get decrypted on the Instagram servers to the User's Profile ID.  On clicking on the link, it would open the Instagram App and plays the reel and then an interruption will be by a popup like the below screenshot  The Attack... Crafting the URL ...  If you replace the <Reel_ID> (What the user intended to share) with a <Granphically_Sensitive_Content_REEL_ID> in the link and send it to users, when ever any user opens the link. It would show graphically sensitive content and then a Popup of the victim's profile. Though they didn't intend to share it.  Report timeline...
Post a Comment
Read more