Risk
7/21/2011
09:21 AM
Connect Directly
RSS
E-Mail
50%
50%

Google Hacking Tools Prepped For Black Hat

'Diggity' family of search tools will help security teams and pen testers find searchable flaws before bad guys, Stach & Liu researchers say.

Go Google-hack yourself.

No, it's not a curse. It's a bit of advice being prepared by two researchers who will present a new batch of search engine-based hacking tools at the Black Hat USA conference in Las Vegas next month.

Fran Brown and Rob Ragan, both researchers at the consulting firm Stach & Liu, are planning to roll out a series of tools--dubbed "Diggity"--that speed the process of finding security vulnerabilities via Google or Bing. The tools are designed to help enterprises "Google hack" themselves to identify potential avenues of attack before the bad guys do.

"We wanted to find a way to bring search engine hacking back into light because it's a pretty effective method of finding vulnerabilities, and we see it being used more and more [by malicious attackers]," Ragan said.

Indeed, just last week, the Stach & Liu researchers offered evidence that the LulzSec hacker group used Google hacking to choose its targets during its run of hacks on the websites and databases of well-known companies and government organizations.

At Black Hat, the researchers will demonstrate how enterprises can use Google hacking tools on themselves to expose flaws in their data and applications that might be found using a search engine. The tools--each of which carries the name "Diggity"--enable enterprises to search across multiple domains to identify Google-searchable flaws that might lead to common attacks, such as SQL injection and cross-site scripting.

"You can do this yourself with Google, but you would typically have to do it on one domain at a time, and that can be incredibly time-consuming when you're an enterprise that has hundreds of domains," Brown says.

Brown compares the Diggity tools to an intrusion detection system that searches for known attacks.

Read the rest of this article on Dark Reading.

Black Hat USA 2011 presents a unique opportunity for members of the security industry to gather and discuss the latest in cutting-edge research. It happens July 30-Aug. 4 in Las Vegas. Find out more and register.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5619
Published: 2014-09-29
The Sleuth Kit (TSK) 4.0.1 does not properly handle "." (dotfile) file system entries in FAT file systems and other file systems for which . is not a reserved name, which allows local users to hide activities it more difficult to conduct forensics activities, as demonstrated by Flame.

CVE-2012-5621
Published: 2014-09-29
lib/engine/components/opal/opal-call.cpp in ekiga before 4.0.0 allows remote attackers to cause a denial of service (crash) via an OPAL connection with a party name that contains invalid UTF-8 strings.

CVE-2012-6107
Published: 2014-09-29
Apache Axis2/C does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

CVE-2012-6110
Published: 2014-09-29
bcron-exec in bcron before 0.10 does not close file descriptors associated with temporary files when running a cron job, which allows local users to modify job files and send spam messages by accessing an open file descriptor.

CVE-2013-1874
Published: 2014-09-29
Untrusted search path vulnerability in csi in Chicken before 4.8.2 allows local users to execute arbitrary code via a Trojan horse .csirc in the current working directory.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.