Facebook Messenger for MacOS contained valid hardcoded FB access token (employee's token?)

By -

 

At summer I decided to test Facebook Messenger for MacOS. Grepped all urls from code and started to analyze them. Quickly I noticed few urls on image with "access_token" value:


Cool! Interesting is this token still valid?

I opened https://developers.facebook.com/tools/debug/accesstoken/?access_token= and got confirmation: the token is valid!

I stopped experiments and rapidly sent report to Facebook Team.




All time before bounty decision I hoped that this token had some extra internal permissions. Unfortunately for me looks like it was just normal token, probably from Facebook employee, without any extra access. I think some software developer placed such link by mistake inside the app and it went over whole world))
So, be careful and attentive when you investigate hardcoded data inside apps ;)

  • Facebook Messenger v. 97.11.116 (97.11.116.283083801) for MacOS
  • Submitted: 27.07.2021 10:08AM
  • Triaged: 27.07.2021 12:36AM
  • Fixed: 27.07.2021 12:45AM (token became invalid, may be system automatically invalidated the token or Facebook team did it)
  • Fix notification: 04.08.2021
  • Reward: $500 (+$125 bonus) 08.09.2021

Popular posts from this blog

Facebook Messenger server random memory exposure through corrupted GIF image

By -
Image
Intro Year ago, in February 2018, I was testing Facebook Messenger for Android looking how it works with corrupted GIF images. I was inspired by Imagemagick "uninitialized memory disclosure in gif coder" bug and PoC called "gifoeb" (cool name for russian speakers). I found Messenger app only crashes with images generated by "gifoeb" tool with Nullpointer dereferrence (Facebook did't awarded bounty for DoS in Facebook Messenger for Android). Ok. I thought: what is GIF image format and how it looks, how I can generate my own image? (spoiler: 10K$ bug in Facebook Messenger for Web, but theory first)
Read more

React debug.keystore key was trusted by Meta(Facebook) which caused to Instagram account takeover by malicious apps.

By -
Image
  App Signing All Android applications should be signed with keys generated by app developers ( https://source.android.com/security/apksigning ). When application signed with specific key we can verify that this app was not modified by thirdparty. Also it is possible to communicate between apps (IPC) and verify app identity by it key signature. If caller app has verified signature than we can allow it to do some restricted actions, for example we can return some confidential information to it like user information. This keys should be confidential and not be exposed outside. Bug Description I played with Facebook Sdk for Android and noticed one thing. This api call is not validates package name when you authorize your client_id ``` https://m.facebook.com/dialog/oauth?android_key= Xo8WBi6jzSxKDVR4drqm84yr9iU &calling_package_key=com.vulnano.android.facebook.sdkat&client_id=124024574287414&display=touch&facebook_sdk_version=8.1.0&redirect_uri=fbconnect%3A%2F%2Fsuccess
Read more

Meta Quest: Attacker could make any Oculus user to follow (subscribe) him without any approval

By -
Image
Description Attacker was able to subscribe any Oculus user on attacker's Oculus account without user approval. So it was possible to make very attractive account with a lot of real followers without their approval:). This followers are displayed in Oculus Quest device when you open user profile, also in profile opened in Meta Quest for Android and some other places. Bug details  This page https://secure.oculus.com/my/people/   displays Oculus user followers:  
Read more