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.

Vulnerabilities / Threats

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

Facebook Patches Critical WhatsApp Security Flaw

Bug gives attackers a way to use GIF images to steal data from Android devices running the message app.

A security researcher this week posted details on a new remotely exploitable vulnerability in WhatsApp that attackers could leverage via a malicious GIF image to steal messages, video, audio, and other content from devices running the app.

The disclosure on GitHub, by a researcher using the handle "Awakened," is the second critical vulnerability involving WhatsApp in recent months, suggesting that secure messaging apps are not as secure as many users might perceive. In May, Facebook, which owns WhatsApp, warned about an attacker — thought to be a private company working on behalf of a government — exploiting a security flaw on WhatsApp to spy on human right organizations.

In the latest case, the bug impacts WhatsApp for Android versions 2.19.230 and before on devices running Android 8.1 and 9.0 devices. Facebook has acknowledged the issue and patched it in the latest WhatsApp version 2.19.244.

The bug does not exist in WhatsApp itself but rather in an open source library that the application uses to parse media files. The so-called double-free vulnerability (tracked as CVE-2019-11932) stems from how memory is allocated when GIF images are parsed in WhatsApp. A double-free vulnerability involves an app calling the same memory space on a device twice, resulting in a memory leak.

"The user's phone may get remotely controlled by the attacker, allowing them to run codes and commands with all WhatsApp permissions," says Pham Hong Nhat, the Vietnamese security researcher who uses the handle Awakened. The vulnerability gives attackers a way to read the contents of the SD card, read the message database, record video and take other actions, he says. The GIF file just needs to be planted on the user's SD card. It can be sent through chat messengers, downloads or emails, he says. Pham says he notified Facebook about the issue in late July to early August.

Ashlee Benge, threat researcher at ZeroFox, says one likely exploitation scenario involves an attacker sending a potential victim a malicious GIF file.

If the attacker's phone number is in the recipient's contacts — which could happen via social engineering, for instance — the GIF file could be downloaded to the recipient's device without any kind of user interaction, Benge says. "Then, when the recipient goes to open the WhatsApp Images folder, like if they were sending an image in a message, the exploit will be triggered," she explains.

If the sender was not a contact, the recipient would have to be tricked into saving the image prior to the exploit being triggered, Benge says.

Not Easy to Exploit
The new vulnerability in WhatsApp is not especially easy to exploit, adds Jonathan Knudsen, senior security strategist at Synopsys. "It's not like the old Ping of Death or the more recent bug where a malformed message would cause an iPhone to fail," he says. The WhatsApp  vulnerability requires the attacker already have another toehold on the target's device. Only then could the attacker be able to deliver a crafted GIF that would take control. An attacker that exploited the flaw would be able to do anything on the device that WhatsApp has permission to access, he says. 

"Successful exploitation of this could trigger the application crashing or, in worst-case scenarios, grant the attacker the ability to execute arbitrary code on a victim's device," Benge says. It could allow attackers to access the WhatsApp message database and other sensitive files on the user device.

The most troubling part about the vulnerability is that it exists in a software component that other application developers are likely using as well. So the threat is not confined just to WhatsApp but to any app using the vulnerable open source media library. There's no telling how many apps use the same library and are similarly vulnerable, Knudsen says.

In a brief statement, a Facebook spokeswoman said the issue was reported to the company and quickly addressed last month. "We have no reason to believe this affected any users, though, of course, we are always working to provide the latest security features to our users.”

Awakened, the security researcher who disclosed the bug, is urging WhatsApp uses to update to the latest version of the messaging apps to stay safe from potential attacks.

"From a user perspective, the most important takeaway is being vigilant about updates," Knudsen says. "Vulnerabilities happen all the time, so the best a user can do is keep software current so that known vulnerabilities are addressed."

Related Content:

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "How the City of Angels Is Tackling Cyber Devilry"

 

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

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Oddissman
50%
50%
Oddissman,
User Rank: Apprentice
10/4/2019 | 9:11:59 AM
i know that...
i know that a major security flaw with WhatsApp could allow hackers to view and manipulate people's private photos and videos. thats why i stopped using it. now i prefer Utopia messenger because it respects my privacy and never gives your data to any advertiser, tracking company or another third party.
Data Privacy Protections for the Most Vulnerable -- Children
Dimitri Sirota, Founder & CEO of BigID,  10/17/2019
Sodinokibi Ransomware: Where Attackers' Money Goes
Kelly Sheridan, Staff Editor, Dark Reading,  10/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-18214
PUBLISHED: 2019-10-19
The Video_Converter app 0.1.0 for Nextcloud allows denial of service (CPU and memory consumption) via multiple concurrent conversions because many FFmpeg processes may be running at once. (The workload is not queued for serial execution.)
CVE-2019-18202
PUBLISHED: 2019-10-19
Information Disclosure is possible on WAGO Series PFC100 and PFC200 devices before FW12 due to improper access control. A remote attacker can check for the existence of paths and file names via crafted HTTP requests.
CVE-2019-18209
PUBLISHED: 2019-10-19
templates/pad.html in Etherpad-Lite 1.7.5 has XSS when the browser does not encode the path of the URL, as demonstrated by Internet Explorer.
CVE-2019-18198
PUBLISHED: 2019-10-18
In the Linux kernel before 5.3.4, a reference count usage error in the fib6_rule_suppress() function in the fib6 suppression feature of net/ipv6/fib6_rules.c, when handling the FIB_LOOKUP_NOREF flag, can be exploited by a local attacker to corrupt memory, aka CID-ca7a03c41753.
CVE-2019-18197
PUBLISHED: 2019-10-18
In xsltCopyText in transform.c in libxslt 1.1.33, a pointer variable isn't reset under certain circumstances. If the relevant memory area happened to be freed and reused in a certain way, a bounds check could fail and memory outside a buffer could be written to, or uninitialized data could be disclo...