{"id":25948,"date":"2019-03-08T02:36:43","date_gmt":"2019-03-08T02:36:43","guid":{"rendered":"https:\/\/packetstormsecurity.com\/news\/view\/29911\/FB-Messenger-Bug-Revealed-Who-You-Had-Conversations-With.html"},"modified":"2019-03-08T02:36:43","modified_gmt":"2019-03-08T02:36:43","slug":"fb-messenger-bug-revealed-who-you-had-conversations-with","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/fb-messenger-bug-revealed-who-you-had-conversations-with\/","title":{"rendered":"FB Messenger Bug Revealed Who You Had Conversations With"},"content":{"rendered":"

\"facebook-f8-2016-mark-zuckerberg-0088\"<\/span><\/span><\/p>\n

Facebook Messenger had a flaw that let potential attackers see who you had conversations with.<\/span><\/p>\n

James Martin<\/span><\/p>\n

Facebook is making a big shift to private messages, but it’s not immune to security vulnerabilities.<\/p>\n

Imperva, a cybersecurity company, on Thursday detailed a flaw with Facebook Messenger that allowed potential attackers to learn who you were talking with on the chatting service.<\/p>\n

The security bug didn’t show the content of the messages, but just knowing who you were in touch with has the potential to harm your privacy, said Ron Masas, the security researcher who discovered the vulnerability.<\/p>\n

“It could be sent to high-profile targets to figure out who they’ve had a conversation with,” Masas said. “If you sent a message to a bot to order pizzas, I would know.”<\/p>\n

Facebook said Thursday it fixed the bug in December. <\/p>\n

“The issue in his report stems from the way web browsers handle content embedded in webpages and is not specific to Facebook,” a Facebook spokesperson said. “We’ve made recommendations to browser makers and relevant web standards groups to encourage them to take steps to prevent this type of issue from happening in other web applications, and we’ve updated the web version of Messenger to ensure this browser behavior isn’t triggered on our service.”<\/p>\n

Masas had also detailed a similar Facebook bug in November<\/a>, where data thieves could see private posts you’ve liked and what your friends have liked.<\/p>\n

The bug worked by analyzing iFrames — the code used to embed content like YouTube videos on pages. In your browser, Messenger loaded a specific number of iFrames for people you’ve had a conversation with and people you’ve never talked to, Masas said.<\/p>\n

The security researcher developed a tool that’d report the number of iFrames loaded, and with that data, he could figure out who someone has been in touch with.<\/p>\n

For the attack to work, the victim would have to click on a link leading to Masas’ tool. In his proof-of-concept, he set the trap link as a video, so that unsuspecting victims would be distracted while that data was siphoned off.<\/p>\n

So in one tab, you’d have the spying tool gathering data on iFrames of the recipient’s Facebook page on another tab.<\/p>\n

“The original tab can ask the browser how many iFrames another tab has,” Masas said. “It looks for this pattern that indicates whether or not you’ve had a conversation with a person.”<\/p>\n

That pattern was a specific drop in iFrames if you’ve never spoken with somebody on Messenger.<\/p>\n

\"screen-shot-2019-03-07-at-11-03-42-am\"<\/span>

\"screen-shot-2019-03-07-at-11-03-42-am\"<\/span><\/p>\n

<\/noscript><\/span><\/p>\n

The blue line indicates you never spoke with someone on Facebook Messenger. The red line means you did. That spike in the iFrames load indicates the difference.<\/span><\/p>\n

Imperva<\/span><\/p>\n

When Masas first reported the flaw to Facebook on Nov. 29, the social network tried fixing it by randomizing the number of iFrames, he said. But even though the specific number of iFrames was removed, that drop in the pattern still existed, Masas said.<\/p>\n

Facebook eventually fixed the flaw by removing iFrames from Messenger altogether.<\/p>\n

The security vulnerability with Facebook Messenger comes a day after Mark Zuckerberg announced his plans for the future of the social network<\/a>. The CEO said Facebook is moving toward a privacy-focused platform, with an emphasis on encrypted messaging.<\/p>\n

But with the bug that Masas discovered, encryption wouldn’t have stopped the flaw, the researcher said.<\/p>\n

That’s because it looked for iFrames, which your browser provided — not Facebook.<\/p>\n

“This data was leaked over the client side. In terms of encryption, it’s not really going to affect this,” he said. <\/p>\n

Originally published at 11 a.m. PT.<\/strong>
Updated at 4:06 p.m.<\/strong>: With a response from Facebook. <\/p>\n