Ever noticed that big blue button on the top of every Facebook page?
This feature, known as
Call to action or
CTA is designed for user engagement and allows a page to redirect their visitors to a website, an app, inbox etc. The documentation for this feature can be found
After a few hours of playing around with the Graph API, I found it was possible for a page admin to abuse this feature and launch Facebook's own internal deeplinks when clicked by another user.
CTA is clicked from a mobile device, a malicious payload could be executed. However, when clicked from the web, it maintains its original functionality.
The impact for this type of vulnerability is that a page admin could perform CSRF / user de-anonymization attacks against its visitors who engage with the
Call to Action button.
Lets dive straight in!
Reproducing the security issue
To reproduce this vulnerability we will make use of Facebooks Graph API.
1. Create a new Facebook page and edit the Action Button
2. Select "Use App", provide a valid URL and click save
3. Take note of the
Call to action id found in the POST request we just made
5. Now we can use the Graph API to include our deeplink. Visit https://developers.facebook.com/tools/explorer/?method=POST&path=XXX&version=v12.0&android_deeplink=fbinternal%3A%2F%2Fsupersecretfbinternallink&android_destination_type=APP_DEEPLINK having XXX as your
By running the above post request, we are updating our current
CTA object to include an android deeplink with a destination type of "APP_DEEPLINK".
5. You will see a response of "Success". If we were to do a Graph API call on the
CTA object again it will now look something like this:
If we were to visit this page from another user via an android device, our internal deeplink will get executed when the visitor clicks the "Use App" button. This behavior can been seen here:
Shortly after the bug was triaged, I revisited the documentation and noticed there were fields called
iphone_destination_type against the
CTA object. By replaying the same post request as before using the iOS keys I was also able to launch internal links on an iOS device.
Timeline - Key dates
- 28 Oct 2021 - Reported to Meta
- 29 Oct 2021 - Triaged
- 24 Jan 2022 - Confirmed vulnerability has been fixed
- 26 Jan 2022 - Bounty issued (89 days in, meaning I missed out on the 10% bonus by 1 day...)
- 02 Feb 2022 - Blog post went live
- 17 Feb 2022 - Blog post taken down - see below update
- 17 Feb 2022 - Facebook investigating further
- 13 Oct 2022 - Clean up made on all CTA objects using an internal deeplink
- 25 Oct 2022 - Confirmed the vulnerability has been fixed
XX XXX 2022 - Additional bounty rewarded
- 14 Dec 2022 - No addtional impact found
Response From Meta Security Team
After reviewing this issue, we have decided to award you a bounty of $4000. Below is an explanation of the bounty amount. Meta fulfills its bounty awards through Bugcrowd and HackerOne.
This issue could have allowed victim's to unintentionally open internal deeplinks.
There seemed to be a bit of confusion as to whether this issue was fully resolved (after bounty). Whilst no one was able to create an internal deeplink via a Graph API request, any deeplink that was already in place could still be executed on the mobile devices. This was brought to Facebooks attention on 17th February in which this blog post was taken down.
However, Facebook had confirmed after some internal checks there was no evidence that this vulnerability had been abused.
Thanks again for your report. We have made a lot of progress about this issue, and after further investigation we may also have found additional impact. We are in the process of removing the previously created call to action button, this should be done shortly. However even after your call to action button with internal deeplinks are deleted please wait until we finish the additional impact investigation too, this may take longer but you may receive additional reward from it.
Thanks for reporting this issue,
Sorry for the delay, we have confirmed with the team, we did not find additional impact from the report, unfortunately we will not be awarding additional bounty for this report.
If you wish to publish a write-up, feel free to provide us a draft version of your write-up, so we can review for accuracy, but only if you want us to do so.
Despite being told there "may" have been additional impact here, Meta finally responded confirming that there was no additional impact. Overall I was left hanging on this report and underpaid 2.5% time bonus.