Vulnerabilities / Threats
06:25 AM
Quick Hits
Quick Hits
Quick Hits
Connect Directly
Repost This

How To Use Google To Find Vulnerabilities In Your IT Environment

The bad guys use search engines to seek out weak spots. Here's how to beat them to the punch

[The following is excerpted from "Using Google To Find Vulnerabilities In Your IT Environment," a new report posted this week on Dark Reading's Vulnerability Management Tech Center.]

The vast volumes of information available on the Internet are of great value to businesses -- and to hackers. For years, hackers have been using Google and other search engines to identify vulnerable systems and sensitive data on publicly exposed networks. The practice, known as Google hacking, has seen a resurgence of late, providing new challenges for IT professionals striving to protect their companies from threats growing in number and sophistication.

Google hacking -- a term used for penetration testing using any search engine -- surged in popularity around 2004, when computer security expert Johnny Long first released his book Google Hacking for Penetration Testers and the Google Hacking Database (GHDB). The database was designed to serve as a repository for search terms, called Google-Dorks, that exposed sensitive information, vulnerabilities, passwords, and much more.

There recently has been an upswing in Google hacking, with a few factors playing a role in the practice’s growth. For one thing, the amount of data indexed and searchable by Google and other search engines has skyrocketed in the last few years. Simply put, this has given hackers much more to work with.

There has also been a significant increase in new search engine interfaces to various types of data. Examples include Google Health and Google Code Search (recently shut down), which have allowed users to search through patient health records and open source code projects, respectively. We’ve also seen the emergence of security-specific search engines such as Shodan come into play. These search engines were created specifically for use by penetration testers to identify vulnerable Web applications on the Internet.

We saw a frightening example last year of just how effective Google hacking can be when the group LulzSec used Google hacking techniques to go on an epic spree that left in its wake a number of victims, including Sony, PBS, Arizona’s Department of Public Safety, FBI affiliate InfraGard, and the CIA.

However, what’s good for hackers is also good for corporate security professionals, who can make use of Google hacking tools and other resources to identify -- and then eliminate -- vulnerabilities in their data systems. The majority of these tools are free and easy to use, although experience and skills associated with Web application security are helpful in validating scan results and identifying which results are real security issues and which are not.

There is no one tool that will serve as a silver bullet in eliminating search engine exposures. We encourage security professionals to try out and regularly use as many as possible to gain as much security coverage as possible over their network perimeter.

For more information on these free tools -- and how to use them to find vulnerabilities in your own environment -- download the full report on Google vulnerability research.

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.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
User Rank: Ninja
3/18/2012 | 6:19:30 PM
re: How To Use Google To Find Vulnerabilities In Your IT Environment
The Yale breach from last year is another example of how Google can be used by attackers to find all sorts of that case, records were exposed for nearly a year.Brian Prince, InformationWeek/Dark Reading Comment Moderator-á
Register for Dark Reading Newsletters
White Papers
Current Issue
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
Published: 2014-04-24
Cisco IOS before 15.3(2)S allows remote attackers to bypass interface ACL restrictions in opportunistic circumstances by sending IPv6 packets in an unspecified scenario in which expected packet drops do not occur for "a small percentage" of the packets, aka Bug ID CSCty73682.

Published: 2014-04-24
Cisco ASR 1000 devices with software before 3.8S, when BDI routing is enabled, allow remote attackers to cause a denial of service (device reload) via crafted (1) broadcast or (2) multicast ICMP packets with fragmentation, aka Bug ID CSCub55948.

Published: 2014-04-24
Cross-site scripting (XSS) vulnerability in IBM SmartCloud Analytics Log Analysis 1.1 and 1.2 before allows remote attackers to inject arbitrary web script or HTML via an invalid query parameter in a response from an OAuth authorization endpoint.

Published: 2014-04-24
The password recovery service in Open-Xchange AppSuite before 7.2.2-rev20, 7.4.1 before 7.4.1-rev11, and 7.4.2 before 7.4.2-rev13 makes an improper decision about the sensitivity of a string representing a previously used but currently invalid password, which allows remote attackers to obtain potent...

Published: 2014-04-24
The E-Mail autoconfiguration feature in Open-Xchange AppSuite before 7.2.2-rev20, 7.4.1 before 7.4.1-rev11, and 7.4.2 before 7.4.2-rev13 places a password in a GET request, which allows remote attackers to obtain sensitive information by reading (1) web-server access logs, (2) web-server Referer log...

Best of the Web