Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

12/17/2019
05:00 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Facebook Fixes WhatsApp Group Chat Security Issue

Flaw allowed attackers to repeatedly crash group chat and force users to uninstall and reinstall app, Check Point says.

Facebook has fixed a bug in its WhatsApp chat platform that gave attackers a way to send a malicious group-chat message capable of repeatedly crashing the entire application for all members of a targeted chat group.

To regain access to the application, the victim would have had to uninstall and reinstall WhatsApp. Without re-installation, the user couldn't return to the chat group because the app would repeatedly crash with each attempt.

The targeted group itself would have to be deleted and restarted, resulting in a complete loss of group chat history, Check Point said.

"The crash-loop is a killing of the app that is unstoppable," says Ekram Ahmed, head of public relations at Check Point. "In the first cycle, the app is crashed. Then the user tries to regenerate the app. The app crashes again without any warning. It's a consistent loop that crashes the app - on and on," he says.

This is the second time in recent months that Check Point has identified an issue in WhatsApp. At Black Hat USA this August, researchers from the company showed how an attacker could intercept and manipulate WhatsApp messages in an individual or group setting to spread fake news and create other problems.  

Check Point researchers used a Web-debugging tool to intercept and decrypt the communication that happens between WhatsApp and WhatsApp Web when a user launches the desktop version of the app. By replacing some of the parameters in that communication, the researchers showed how they could change the content of chat messages and impersonate others.

At the time, Facebook described the issue as having nothing to do with the security of the end-to-end encryption on its messaging platform. The company has instead said the issue is similar to someone altering the contents of an email message. More than 500 million people worldwide on average are active on WhatsApp daily, according to Statista.

The latest — and now patched — exploit involves the same communication between the mobile and Web version of WhatsApp. In this case, the researchers found that by examining and manipulating one specific message parameter containing a message sender's phone number, they could cause the app to crash for all members in a chat group.

An attacker would first need to gain access to a target group and assume the identity of a group member, which in this case could be accomplished by manipulating the message parameter containing the user's phone number, Ahmed says. WhatsApp allows for up to 256 members to be part of a single group.

The attacker could then edit other specific message parameters and create a malicious message that is sent to all members in a targeted group, causing the crash-loop.

Check Point reported the issue to WhatsApp's bug bounty program in August and the issue was quickly resolved, the security vendor said. A fix for the flaw is available in WhatsApp version 2.19.58 and users should manually apply it as soon as possible, Check Point advised.

Erich Kron, security awareness advocate at KnowBe4, said that while the bug is destructive and inconvenient, it at least does not enable the content of conversations or personal data to be exposed. Apple Store currently does not have the new fixed version of WhatsApp available for download, he noted, but users should keep checking and apply the patch as soon as it becomes available.

Related Content:

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "Disarming Disinformation"

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20934
PUBLISHED: 2020-11-28
An issue was discovered in the Linux kernel before 5.2.6. On NUMA systems, the Linux fair scheduler has a use-after-free in show_numa_stats() because NUMA fault statistics are inappropriately freed, aka CID-16d51a590a8c.
CVE-2020-29368
PUBLISHED: 2020-11-28
An issue was discovered in __split_huge_pmd in mm/huge_memory.c in the Linux kernel before 5.7.5. The copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check, aka CID-c444eb564fb1.
CVE-2020-29369
PUBLISHED: 2020-11-28
An issue was discovered in mm/mmap.c in the Linux kernel before 5.7.11. There is a race condition between certain expand functions (expand_downwards and expand_upwards) and page-table free operations from an munmap call, aka CID-246c320a8cfe.
CVE-2020-29370
PUBLISHED: 2020-11-28
An issue was discovered in kmem_cache_alloc_bulk in mm/slub.c in the Linux kernel before 5.5.11. The slowpath lacks the required TID increment, aka CID-fd4d9c7d0c71.
CVE-2020-29371
PUBLISHED: 2020-11-28
An issue was discovered in romfs_dev_read in fs/romfs/storage.c in the Linux kernel before 5.8.4. Uninitialized memory leaks to userspace, aka CID-bcf85fcedfdd.