Vulnerabilities / Threats

10/1/2015
05:00 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Stagefright 2.0 Vuln Affects Nearly All Android Devices

Worst threat is only to version 5.0 Lollipop and later.

Once again, Android has been found slashed wide open to a critical vulnerability in its multimedia engine that is easy to exploit, enables remote privileged code execution, requires no user interaction, and affects nearly every Android device.

The so-called Stagefright 2.0 impacts over one billion Android devices, almost every one since version 1 was released in 2008 (although it's of greatest concern to version 5.0 Lollipop and later, which is only about 21 percent of Androids in use). 

Like its predecessor, Stagefright 2.0 was discovered by Zimperium Mobile Threat Protection, zLabs VP of Research Joshua J. Drake. Stagefright 2.0 is actually a set of two vulnerabilities in the way Android processes multimedia files. The first, CVE-2015-6602, is a vulnerability in libutils versions 1.0 and later. The second (which has not yet been assigned a CVE number) is in libstagefright versions 5.0 and later. The second bug triggers the first one, so Androids from version 5.0 and later are particularly at risk. In older devices, CVE-2015-6602 could be compromised by third-party apps or vendors/carrier functions that call libutils.

"The impact and severity of this pair of vulnerabilities is nearly identical to the original Stagefright issues," says Drake.

Stagefright 2.0 could be exploited via a malicious audio or video file. The bug is in how Android processes metadata, so the target doesn't need to actually open the audio or video file, but merely preview it. When Drake announced the original Stagefright at the end of July ahead of the Black Hat USA conference, the scariest attack vector proposed was via MMS message; because all an attacker would need is a phone number.

“At BlackHat USA 2015, Google announced that updated versions of Hangouts and Messenger were released to remove automatic processing of media received by MMS," Drake says. "However, nothing was done to prevent a user from interacting with media and Hangouts/Messenger remain a viable, though less attractive, attack vector.”

Drake says Stagefright 2.0's more likely to be exploited via browser-based attacks -- phishing messages, malvertising, man-in-the-middle attacks -- or via third-party apps that call to the vulnerable library.

The question with Stagefright 2.0, as with earlier core issues in Android, is how effective the Android ecosystem -- a sprawling patchwork of handset manufacturers, carriers, and third-party developers -- will be at delivering fixes. Zuk Avraham, founder, chairman and CTO at Zimperium, says that the Android ecosystem has "absolutely" changed its security behavior since the original Stagefright was revealed.

"Following the first Stagefright discovery and the announcement of Zimperium Handset Alliance (ZHA), device vendors and carriers united to offer shorter patch cycles for critical security incidents. We are excited to have made such an impact on the ecosystem," Avraham says.

"The advice I give friends and family is to buy handsets that allow for updates directly from the manufacturer," says Trey Ford, global security strategist at Rapid7. "For those who love Android -- buy directly from Google to remove the carrier-introduced delay when Android releases a security patch. For Google, this is an ecosystem problem. Google manages Android, and does a respectable job shipping patches. They deliver to the carriers, which in turns, the carriers take some time (picture 9-18 months) before those patches are certified and delivered over the air to the devices," Ford says. "In other cases, they don’t bother, as the handset life expectancy is so brief for the consumer. Discerning consumers are paying attention, they want to keep their patches up to date."

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Mariodelavega
50%
50%
Mariodelavega,
User Rank: Apprentice
10/5/2015 | 6:47:16 AM
Re: reply
Well thats right but doesnt work everytime tho..
qwerty@mine
0%
100%
[email protected],
User Rank: Apprentice
10/2/2015 | 8:17:54 AM
reply
i think we can protect ourselves by using anti malware tools
WebAuthn, FIDO2 Infuse Browsers, Platforms with Strong Authentication
John Fontana, Standards & Identity Analyst, Yubico,  9/19/2018
Turn the NIST Cybersecurity Framework into Reality: 5 Steps
Mukul Kumar & Anupam Sahai, CISO & VP of Cyber Practice and VP Product Management, Cavirin Systems,  9/20/2018
NSS Labs Files Antitrust Suit Against Symantec, CrowdStrike, ESET, AMTSO
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/19/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-11763
PUBLISHED: 2018-09-25
In Apache HTTP Server 2.4.17 to 2.4.34, by sending continuous, large SETTINGS frames a client can occupy a connection, server thread and CPU time without any connection timeout coming to effect. This affects only HTTP/2 connections. A possible mitigation is to not enable the h2 protocol.
CVE-2018-14634
PUBLISHED: 2018-09-25
An integer overflow flaw was found in the Linux kernel's create_elf_tables() function. An unprivileged local user with access to SUID (or otherwise privileged) binary could use this flaw to escalate their privileges on the system. Kernel versions 2.6.x, 3.10.x and 4.14.x are believed to be vulnerabl...
CVE-2018-1664
PUBLISHED: 2018-09-25
IBM DataPower Gateway 7.1.0.0 - 7.1.0.23, 7.2.0.0 - 7.2.0.21, 7.5.0.0 - 7.5.0.16, 7.5.1.0 - 7.5.1.15, 7.5.2.0 - 7.5.2.15, and 7.6.0.0 - 7.6.0.8 as well as IBM DataPower Gateway CD 7.7.0.0 - 7.7.1.2 echoing of AMP management interface authorization headers exposes login credentials in browser cache. ...
CVE-2018-1669
PUBLISHED: 2018-09-25
IBM DataPower Gateway 7.1.0.0 - 7.1.0.23, 7.2.0.0 - 7.2.0.21, 7.5.0.0 - 7.5.0.16, 7.5.1.0 - 7.5.1.15, 7.5.2.0 - 7.5.2.15, and 7.6.0.0 - 7.6.0.8 as well as IBM DataPower Gateway CD 7.7.0.0 - 7.7.1.2 are vulnerable to a XML External Entity Injection (XXE) attack when processing XML data. A remote atta...
CVE-2018-1539
PUBLISHED: 2018-09-25
IBM Rational Engineering Lifecycle Manager 5.0 through 5.02 and 6.0 through 6.0.6 could allow remote attackers to bypass authentication via a direct request or forced browsing to a page other than URL intended. IBM X-Force ID: 142561.