Tuesday, April 8, 2025
HomeCVE/vulnerabilityFacebook Messenger Bug Let Android Users Spy On Each Other

Facebook Messenger Bug Let Android Users Spy On Each Other

Published on

SIEM as a Service

Follow Us on Google News

Tamagotchi hacker, Natalie Silvanovich, who works as a Security Engineer on Prjoect Zero at Google recently received a bounty of $60,000 for identifying a bug in Facebook Messenger which allows a call to connected much before the callee has answered the call. The bug seems to exist on the Android Facebook messenger app only.

Facebook Messenger sets up audio and video calls in WebRTC by exchanging a series of thrift messages between the callee and caller. WebRTC is a free, open-source project that provides web browsers and mobile applications with real-time communication via simple application programming interfaces.

Usually in an audio call, audio is transmitted only when the callee has attended the call. However, there is an instance when the call transmitting audio even before the recipient of the call can accept the call. This allows any miscreant to monitor the victim’s surroundings.

- Advertisement - Google News

Surprised? So are we!! Let’s have a look at how this can be re-created.

1) Log into Facebook Messenger on the attacker device
2) Log into Facebook Messenger on the target device. Also log into Facebook in a browser on the same account. (This will guarantee call set-up uses the delayed calls to setLocalDescription strategy, this PoC doesn’t work with the other strategy)
3) install frida on the attacker device, and run Frida server
4) make a call to any device with the attacker device to load the RTC libraries so the can be hooked with Frida
5) unzip sdp_update, and locally in the folder, run:

python2 modifyout(.)py “attacker device name”

(to get a list of devices, run python2 modifyout(.)py

6) make an audio call to the target device

In a few seconds, audio from the target devices can be heard through the speakers of the attacker device.

The PoC performs the following steps:

1) Waits for the offer to be sent, and saves the sdpThrift field from the offer
2) Sends an SdpUpdate message with this sdpThift to the target
3) Sends a fake SdpAnswer message to the *attacker* so the device thinks the call has been answered and plays the incoming audio

Unusual? Yes!

Common? More than you think

In early 2019, Apple’s Facetime had a similar bug whereby you could listen to the listen in on someone, even if they have not picked the call.

The smartphone may really be much smarter than we can imagine.

You can follow us on LinkedinTwitterFacebook for daily Cybersecurity and hacking news updates.

Also Read

Facebook Taken Down Number of Political ads due to Technical Flaws in their System

Facebook Hacking made Easy and Convenient with Numerous Hacking Apps

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

Threat Actor Leaks Data from Major Bulletproof Hosting Provider Medialand

A threat actor disclosed internal data from Medialand, a prominent bulletproof hosting (BPH) provider...

Morphing Meerkat: A PhaaS Utilizing DNS Reconnaissance to Generate Targeted Phishing Pages

Originally discovered in 2020 as a Phishing-as-a-Service (PhaaS) platform, Morphing Meerkat has since evolved...

Hackers Abuse Windows .RDP Files to Launch Unauthorized Remote Desktop Sessions

The Google Threat Intelligence Group (GTIG) has unearthed a novel phishing campaign leveraging Windows...

Linux 6.15-rc1 Released: Better Drivers, Faster Performance

The Linux kernel community has witnessed another milestone with the release of Linux 6.15-rc1,...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Threat Actor Leaks Data from Major Bulletproof Hosting Provider Medialand

A threat actor disclosed internal data from Medialand, a prominent bulletproof hosting (BPH) provider...

Morphing Meerkat: A PhaaS Utilizing DNS Reconnaissance to Generate Targeted Phishing Pages

Originally discovered in 2020 as a Phishing-as-a-Service (PhaaS) platform, Morphing Meerkat has since evolved...

Hackers Abuse Windows .RDP Files to Launch Unauthorized Remote Desktop Sessions

The Google Threat Intelligence Group (GTIG) has unearthed a novel phishing campaign leveraging Windows...