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

Botnets And Google Dorks: A New Recipe For Hacking

Attackers finding new ways to automate the hunt for vulnerabilities, Imperva researchers say

Google, hackers have discovered, is very good at finding Web-facing security vulnerabilities. But searching for one vulnerability at a time can be slow -- so it's time to automate.

Attackers are now using botnets and Google "dorks" -- clearly defined search parameters -- to speed the process of finding exploitable flaws on the Internet, according to a new report issued today by researchers at Imperva.

"What the hackers are doing is building an army of zombies to perform automated cyber-reconnaissance," says Noa Bar Yosef, senior security strategist at Imperva. "This makes the Google search much more efficient, and it also makes it harder to detect, because each zombie only issues two to four queries per minute, which is not enough to raise a red flag."

"Search engines can be directed to return results that are focused on specific potential targets by using a specific set of query operators," the Imperva report explains. "For example, the attacker may focus on all potential victims in a specified geographic location. In this case, the query includes a 'location' search operator.

"In another scenario, an attacker may want to target all vulnerabilities in a specific website, and achieves this by issuing different queries containing the 'site' search operator," the report continues. "These particular search queries are commonly referred to as 'Google dorks,' or simply 'dorks.'

"Automating the query and result parsing enables the attacker to issue a large number of queries, examine all the returned results, and get a filtered list of potentially exploitable sites in a very short time and with minimal effort."

In some cases, the Dork might focus on a particular application that is known to be vulnerable, Bar Yosef says. It's possible, for example, that a Google Dork search might be responsible for the recent rash of infections found on websites running the osCommerce application -- researchers at Armorize now report that this infection has hit more than 8 million Web pages.

"With a list of potentially vulnerable resources, the attacker can create, or use a ready-made, script to craft targeted attack vectors that attempt to exploit vulnerabilities in pages retrieved by the search campaign," the Imperva report says. "Attacks include infecting Web applications, compromising corporate data, or stealing sensitive personal information."

There's no easy defense against a botnet and a dork search, Bar Yosef says. "If you're online, you're vulnerable," she says. "Your best bet is to assume that your vulnerabilities will be exploited, and take the next steps to mitigate those attacks."

One step that enterprises can take is simply to Google themselves for vulnerabilities, using dorks or other tools to help locate the search engine-facing flaws they could be presenting to hackers. But even a thorough search might not turn up all of the vulnerabilities in your Web-facing systems, Bar Yosef says.

"One thing we need to do is to call upon Google and the other search engines to help," Bar Yosef says. "The search engines may be able to detect this type of activity on their sites and blacklist those who are doing it, or they may be able to tell users when their computers have been compromised, as they have done already in some cases."

In the near term, however, it's likely that the botnet-based search methods will continue to evolve and proliferate, Bar Yosef says. "Attackers are using botnets now to abuse search engines, just as they used them to distribute spam," she says. "What that says is that hackers could go after smaller companies as well as larger enterprises. Everyone could be a target."

Have a comment on this story? Please click "Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... 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 7/6/2020
Ripple20 Threatens Increasingly Connected Medical Devices
Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
Dark Reading Staff 6/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15505
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1, and Sentry before 9.7.3 and 9.8.x before 9.8.1, allow remote attackers to execute arbitrary code via unspecified vectors.
CVE-2020-15506
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1 allow remote attackers to bypass authentication mechanisms via unspecified vectors.
CVE-2020-15507
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1 allow remote attackers to read files on the system via unspecified vectors.
CVE-2020-15096
PUBLISHED: 2020-07-07
In Electron before versions 6.1.1, 7.2.4, 8.2.4, and 9.0.0-beta21, there is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions. Apps using "contextIsolation" are affecte...
CVE-2020-4075
PUBLISHED: 2020-07-07
In Electron before versions 7.2.4, 8.2.4, and 9.0.0-beta21, arbitrary local file read is possible by defining unsafe window options on a child window opened via window.open. As a workaround, ensure you are calling `event.preventDefault()` on all new-window events where the `url` or `options` is not ...