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.

Threat Intelligence

checkLoop 1checkLoop 2checkLoop 3
12/2/2019
04:45 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

StrandHogg Vulnerability Affects All Versions of Android

The bug enables malware to pose as any legitimate Android app, letting attackers track messages, photos, credentials, and phone conversations.

A newly discovered vulnerability in the Android operating system could let attackers abuse legitimate apps to deliver malware. In doing so, they could track users without their knowledge.

Researchers with Norwegian app security company Promon dubbed the bug "StrandHogg," an old Norse term for a Viking coastal raiding tactic. A successful attacker could exploit the vulnerability to take over a legitimate application and run malicious processes without the user's knowledge. StrandHogg has already been exploited in the wild, does not need root access to run, and affects all versions of Android, including Android 10, released in September.

If successful, the vulnerability could grant attackers access to private SMS conversations, photos, and login credentials. They could track a victim's movements, make and/or record phone calls, and spy through the smartphone's camera and microphone, the experts report.

Promon researchers found StrandHogg when its customer, an Eastern European security firm, noticed a trend of money being siphoned from accounts at Czech banks. They traced the root of the problem to StrandHogg, a vulnerability that can be exploited to trick Android users into thinking they're using a legitimate app while interacting with the overlay of a malicious one.

The researchers teamed up with US security firm Lookout, which confirmed 36 malicious apps are exploiting StrandHogg. All of the 500 most popular Android apps are at risk of having their processes abused by the vulnerability. Promon CTO Tom Lysemose Hansen says the bug has been undergoing analysis throughout the spring and summer, though malicious apps could have been exploiting the flaw long before this.

Researchers determined 60 separate financial firms are being targeted with apps designed to exploit this vulnerability. Among the 36 malicious apps exploiting StrandHogg are variants of the BankBot banking Trojan, which has been seen in attacks all over the world since 2017.

How It Works
StrandHogg exists in the Android OS, specifically in the way it switches from process to process for different applications. The weakness is in Android's multitasking system, or its ability to run several apps at the same time and switch from app to app on the screen. Android control setting taskAffinity lets any app, even malicious, take on any identity in the multitasking system.

As a result, malicious apps can request any permission while pretending to be legitimate. An attack could be designed to ask for permissions that seem natural for the targeted apps. By doing this, adversaries could lower the chance of victims realizing something is wrong. Users have no indication they're granting permission to a malicious app and not the authentic one.

"If it wanted to harvest different permissions – say it wants access to SMS and doesn't have that permission when downloaded – then, for example, it can wait until the end user clicks the SMS app and, at that point, take control, ask the user to give permissions, and as the end user clicks the app it provides those permissions," says Hansen. "The end user would believe he gave [permissions] to the SMS app ,but [he] really gave it to the malware app."

(Image: Promon)

(Image: Promon)

The malicious applications exploiting StrandHogg don't directly come from Google Play. Victims have to first download the legitimate application, which serves as a dropper to download future malware, Hansen explains. When the user taps the icon of a legitimate app, the interface of a malicious app instead appears on screen to request permissions or credentials, he continues.

"Just by looking at the first app, it can be very, very difficult to see something is wrong," Hansen adds.

The malware analyzed by Promon was installed through several dropper apps and hostile downloaders distributed on Google Play, researchers explain in a blog post on their findings. While these apps have since been taken down, dropper apps continue to be published and often fly under the radar, generating millions of downloads before they're spotted and deleted.

Promon reported the bug to Google over the summer. While the affected apps have been removed, the StrandHogg has not yet been fixed for any version of Android, researchers say. After 90 days, the problem had still not been addressed.

"We appreciate the researchers work, and have suspended the potentially harmful apps they identified," a Google spokesperson said in response. "Google Play Protect detects and blocks malicious apps, including ones using this technique. Additionally, we're continuing to investigate in order to improve Google Play Protect's ability to protect users against similar issues."

Related Content:

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "A Cause You Care About Needs Your Cybersecurity Help."

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

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
Data Leak Week: Billions of Sensitive Files Exposed Online
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/10/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Our Endpoint Protection system is a little outdated... 
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19777
PUBLISHED: 2019-12-13
stb_image.h (aka the stb image loader) 2.23, as used in libsixel and other products, has a heap-based buffer over-read in stbi__load_main.
CVE-2019-19778
PUBLISHED: 2019-12-13
An issue was discovered in libsixel 1.8.2. There is a heap-based buffer over-read in the function load_sixel at loader.c.
CVE-2019-16777
PUBLISHED: 2019-12-13
Versions of the npm CLI prior to 6.13.4 are vulnerable to an Arbitrary File Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a serve binary, any subsequent installs of pa...
CVE-2019-16775
PUBLISHED: 2019-12-13
Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It is possible for packages to create symlinks to files outside of thenode_modules folder through the bin field upon installation. A properly constructed entry in the package.json bin field would allow a package publi...
CVE-2019-16776
PUBLISHED: 2019-12-13
Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It fails to prevent access to folders outside of the intended node_modules folder through the bin field. A properly constructed entry in the package.json bin field would allow a package publisher to modify and/or gain...
checkLoop 4