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

5/26/2020
05:25 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
100%
0%

StrandHogg 2.0 Emerges as 'Evil Twin' to Android Threat

The vulnerability, which exists in almost every version of Android, is both more dangerous and harder to detect than its predecessor.

A newly discovered Android vulnerability could enable attackers to access most applications on a target device if exploited, researchers report. StrandHogg 2.0, which affects most versions of Android, lets malicious apps pose as legitimate apps while hiding from victims.

Promon researchers named the vulnerability for its similarities to StrandHogg, a flaw the same organization found in late 2019. StrandHogg, named after an old Norse term for a Viking coastal-raiding tactic, could enable attackers to abuse legitimate apps to deliver malware so they can track users without their knowledge. At the time it was disclosed, the flaw had been exploited in the wild and affected all versions of Android up to Android 10.

StrandHogg 2.0 does not affect devices running Android 10, though researchers note many still run older versions. They cite Google data showing that as of April 2020, 91.8% of Android users are on version 9.0 or earlier: Pie (2018), Oreo (2017), Nougat (2016), Marshmallow (2015), Lollipop (2014), Kit Kat (2013), Jellybean (2012), and Ice Cream Sandwich (2011).

Researchers have not seen any malware using StrandHogg 2.0 in the wild. However, they call this flaw the "evil twin" of its predecessor because it enables broader attacks, is harder to detect, and lets attackers take advantage of nearly any application on a target smartphone. They believe StrandHogg's operators have learned and subsequently evolved their tactics. 

The first iteration of StrandHogg exploited the Android control setting TaskAffinity. This flaw takes advantage of Android's multitasking feature and leaves behind traceable pointers. The second version uses a technique that makes this threat harder for victims to detect.

StrandHogg 2.0 is executed through reflection, explains researcher John Høegh-Omdal in a blog post on the discovery. This means malicious applications can assume identities of legitimate apps while staying hidden. Once an attacker's app is downloaded, they can use StrandHogg 2.0 to access text messages and photos, steal login credentials, track GPS movements, make and record phone calls, and/or spy through the camera or microphone. 

The attack begins when a victim clicks the app icon of a legitimate app. But instead of viewing the legitimate app, the malware is displayed and can request permissions under the disguise of legitimate software. It may also appear as a malicious login page. The victim unknowingly grants permission or sends data to the attacker, who then is redirected to the legitimate app. With this level of access, an intruder can proceed to upload data from a victim's device.  

Like its "relatively less evil twin," StrandHogg 2.0 is "extremely dangerous" because it does not need root access or Android permissions to run, Høegh-Omdal wrote. It can hijack permissions of other apps with access to contacts or messages. Unlike its predecessor, which can only attack one app at a time, StrandHogg 2.0 can simultaneously attack multiple apps.

Høegh-Omdal anticipates malware exploiting StrandHogg 2.0 will be harder for antivirus and security scanners to detect. No external configuration is required to execute StrandHogg 2.0, giving attackers a chance to further obfuscate their operations. As he points out, code that comes from Google Play won't initially seem malicious to developers or security teams.

"Promon predicts that attackers will look to utilise both StrandHogg and StrandHogg 2.0 together because both vulnerabilities are uniquely positioned to attack devices in different ways, and doing so would ensure that the target area is as broad as possible," he wrote. Many mitigations that protect against StrandHogg don't work for StrandHogg 2.0, and vice versa.

StrandHogg 2.0 (CVE-2020-0096) has been classified as Critical by Google, which released a patch to Android ecosystem partners last month. A security fix for Android versions 8.0, 8.1, and 9.0 will be rolled out to the general public this month, Promon wrote in a blog post.

Related Content:

 

 
 
 
 
 
 
Learn from industry experts in a setting that is conducive to interaction and conversation about how to prepare for that "really  bad day" in cybersecurity. Click for more information and to register
Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...