'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.
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.
Published: 2015-03-30 The default soap.wsdl_cache_dir setting in (1) php.ini-production and (2) php.ini-development in PHP through 5.6.7 specifies the /tmp directory, which makes it easier for local users to conduct WSDL injection attacks by creating a file under /tmp with a predictable filename that is used by the get_s...
Published: 2015-03-30 The mconvert function in softmagic.c in file before 5.21, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not properly handle a certain string-length field during a copy of a truncated version of a Pascal string, which might allow remote atta...
Published: 2015-03-30 readelf.c in file before 5.22, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not consider that pread calls sometimes read only a subset of the available data, which allows remote attackers to cause a denial of service (uninitialized memory ...
Published: 2015-03-30 Heap-based buffer overflow in the enchant_broker_request_dict function in ext/enchant/enchant.c in PHP before 5.4.38, 5.5.x before 5.5.22, and 5.6.x before 5.6.6 allows remote attackers to execute arbitrary code via vectors that trigger creation of multiple dictionaries.
Published: 2015-03-30 The GetCode_ function in gd_gif_in.c in GD 2.1.1 and earlier, as used in PHP before 5.5.21 and 5.6.x before 5.6.5, allows remote attackers to cause a denial of service (buffer over-read and application crash) via a crafted GIF image that is improperly handled by the gdImageCreateFromGif function.