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

4/16/2019
04:55 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Threat Group Exploits Chrome Bug to Serve Malicious Ads to iOS Users

A new exploit developed by eGobbler is allowing it to distribute malvertisements-more than 500 million to date-at huge scale, Confiant says.

In one of the biggest malvertising campaigns in the last 18 months, a previously known threat group called eGobbler is taking advantage of a security bug in Google's Chrome browser to target millions of iOS users. 

Security vendor Confiant, which has been tracking the campaign since it launched April 6, estimates that more than 500 million malicious ads have been served to iOS users already. Users are being redirected to scam "You've won a gift card" landing pages hosted on a top-level domain previously associated with eGobbler.

Google, which makes most of its money from online advertisements, is currently working on a fix for the bug after being notified about the issue April 11, Confiant said in a report Tuesday. The company did not respond immediately to a request for comment.

According to Confiant, the problem exists in the manner in which Chrome for iOS handles pop-ups. Like other browsers, Chrome incorporates ad sandboxing features to ensure that any code used to insert ads into a Web page only has limited ability to interact with other components.

Sandboxing is a method of restricting what actions are available to any advertisement that is served from a different domain than the page hosting it, says Eliya Stein, senior security engineer at Confiant. The goal is to prevent malicious advertisements from hijacking browser sessions via pop-ups and redirects to websites and landing pages the user did not intend to visit.

Normally, an ad sandbox should prevent a pop-up from being launched unless the user takes some direct action to enable it. The Chrome vulnerability allows attackers a way around this protection.

Chrome Sandboxing Fail
According to Stein, the exploit that eGobbler has developed and is using with such success essentially tricks Chrome for iOS into allowing pop-ups without any direct interaction. "The security bug in Chrome is around Chrome’s built-in pop-up blocker," Stein says. "All versions of Chrome on iOS are impacted."

Because the eGobbler exploit allows the attacker to redirect a user with a pop-up, any other standard sandboxing protections that Chrome has against browser redirections, such as disallowing JavaScript, are moot, he says. "We believe that this exploit was key in magnifying the impact of this attack," Stein says.

He adds that Confiant wants to give Google's Chrome team a reasonable amount of time to fix the bug before releasing more details on how it works. Confiant will release a full analysis of the bug at a later date.

So far, eGobbler has launched eight individual malvertising campaigns mostly targeting iOS users in the US over a six-day period starting April 6. Each individual campaign has lasted between one to two days, Confiant said.

The threat group managed to place over 30 malicious advertisements on legitimate but previously compromised ad servers and used cloaked intermediate CDN domains as part of their ad delivery.

"The CDN domains are used to host the payload that performs the actual redirect and/or the pop-up," Stein says. These are intermediate domains in the ad-serving process that attackers often use for loading ad-serving code. "Attackers rotate these kinds of domains often in attempt to fly under the radar," Stein noted.

The original campaign targeting iOS users has now pivoted to another platform and is ongoing, though Stein declined to name the targeted platform. It is not clear whether eGobbler is exploiting the same Chrome bug, but chances are high they are, he says. "This requires some follow-up on our end," Stein says.

Related Content:

 

 

 

Join Dark Reading LIVE for two cybersecurity summits at Interop 2019. Learn from the industry's most knowledgeable IT security experts. Check out the Interop agenda here.

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
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...