Affiliate Disclosure
If you buy through our links, we may get a commission. Read our ethics policy.

Group FaceTime exploit lets callers listen in on recipient's audio before accepting call [u: fix coming]

Last updated

Until a bug in iOS 12.1 or later is fixed, an exploit allows a FaceTime Video caller to hear the audio, and potentially see video, from the recipient's iPhone without the call even being picked up.

First spotted on social media, the procedure to induce the bug is fairly simple. The caller starts a FaceTime video call with a contact, then while the call is "ringing," they add themselves to the call as a third party by tapping Add Person and entering their own phone number.

If properly executed, a Group FaceTime call is started and the original recipient's audio begins to stream before the call is accepted.

While AppleInsider has duplicated the bug on an iPhone X, iPhone XR, iPhone XS Max, it does not seem to cross over to a Mac accepting a call from an iPhone with Handoff. That said, the recipient iPhone's audio is still sent to the caller. The audio is not bi-directional, and streams from the recipient to the caller only.

Obviously, this does not allow anybody to listen in on any other iPhone surreptitiously, as the call still has to be made in the first place. The recipient's phone will indicate that there is an incoming FaceTime call. Some users, like The Verge's Dieter Bohn, have seen camera access enabled when interacting with an iPhone's power button to dismiss a call, though AppleInsider was unable to confirm.

Until Apple specifically addresses the issue, the safest course is to assume that any incoming FaceTime call is being listened in on by the caller.

Those concerned can disable FaceTime by navigating to Settings > FaceTime and toggling the FaceTime button to the off position.

AppleInsider has reached out to Apple about the issue.

Update: Apple in a statement to BuzzFeed confirmed it is aware of the issue and has "identified a fix that will be released in a software update later this week."



11 Comments

focher 686 comments · 16 Years

That's a pretty bad bug. Not empty-root-password level, but pretty bad.

mazda 3s 1598 comments · 16 Years

Well, that's... disconcerting. How do you even let a bug like this slip through the QA process? 

ericthehalfbee 4489 comments · 13 Years

Haven’t had a chance to try this yet, but I know if I initiate a regular FaceTime call that after several “rings” and no response the call ends with the message “unavailable”. Meaning you would only get audio for a few seconds before the call fails.

When doing a Group FaceTime using this method, does the call still time out and end? Or can you theoretically listen for as long as you want?Edited: Just read The Verge article and they said the problem is more serious on a Mac because “it rings for much longer”. This implies that you can only “listen in” while it’s ringing and not indefinitely.

randominternetperson 3101 comments · 8 Years

mazda 3s said:
Well, that's... disconcerting. How do you even let a bug like this slip through the QA process? 

Because no one thought to create a test script that involved adding a second person to a call before the first person answers?  Seems like a reasonable QA oversight to me.  Now whether it's an "excusable" design/coding error on the other hand...

rogifan_new 4297 comments · 9 Years

So is this a major bug or just techie Twitter freaking out like normal?