Google hacking

Google hacking, also named Google dorking,[1][2] is a hacker technique that uses Google Search and other Google applications to find security holes in the configuration and computer code that websites are using.[3] Google dorking could also be used for OSINT.

Basics

"Google hacking" involves using advanced operators in the Google search engine to locate specific errors of text within search results. Some of the more popular examples are finding specific versions of vulnerable Web applications. A search query with intitle:admbook intitle:Fversion filetype:php would locate all web pages that have that particular text contained within them. It is normal for default installations of applications to include their running version in every page they serve, for example, "Powered by XOOPS 2.2.3 Final".

Devices connected to the Internet can be found. A search string such as inurl:"ViewerFrame?Mode=" will find public web cameras.

Another useful search is following intitle:index.of followed by a search keyword. This can give a list of files on the servers. For example, intitle:index.of mp3 will give all the MP3 files available on various types of servers.

You can use symbols or words in your search to make your search results more precise.[4]

  • Google Search usually ignores punctuation that isn’t part of a search operator.[4]
  • Don’t put spaces between the symbol or word and your search term. A search for site:nytimes.com will work, but site: nytimes.com won’t.[4]

Advanced operators

Many similar advanced operators can be used to exploit insecure websites:

Operator ExamplePurposeMixes with Other Operators?Can be used Alone?WebImagesGroupsNews
site site:wikipedia.orgSearch specific siteyesyesnoyesyescompletely
related related:wikipedia.org Search for related sites yes yes
cache cache:wikipedia.org Search with Google's cached version of a site yes yes
intitle intitle:wikipediaSearch page Titleyes yesyesyesyesyes
allintitle[5] intitle:wikipediaSearch page titleyesyesyesyesyesyes
subject Group subject searchyesyeslike intitlelike intitleyeslike intitle
inurl inurl:wikipediaSearch URLyesyesnoyescompletelylike intitle
allinurl allinurl:wikipediaSearch URLyesyesyesyesyeslike intitle
filetype:env filetype:pdfspecific filesyesyesyesyescompletely
intext intext:wikiSearch text of page onlyyesyesyesyesyesyes
allintext allintext:wikiSearch text of page onlyyesyesyesyesno
"" "Wikipedia" Search for exact word match yes yes
+ jaguar + car Search for more than one specific key yes yes
- jaguar speed -car Exclude words from your search yes yes
OR jaguar OR car Combines two searches yes yes
* how to * to Wikipedia Wildcard operator yes yes
link link:wikipediaSearch for links to pagesyesyesyesyesyescompletely
inanchor Search link anchor textyesyesyesyescompletelyyes
numrange Locate numberyesyesyesyesyescompletely
daterange Search in date rangeyesyesyescompletelycompletelycompletely
author Group author searchyesyesyesyesyescompletely
group Group name searchyesyesyesyescompletely
msgid Group msgid searchyesyescompletelyyes
imagesize imagesize:320x320 Advanced Image Search
@ @wikipedia Search Social Media yes yes
# #wiki Search for hashtags yes yes
$ camera $400 Search for a price yes yes
.. camera $50..$100 Search within a range of numbers yes yes

For a list of operators, refer to Google Search Help

History
See also: Johnny Long § Google hacking

The concept of "Google hacking" dates back to 2002, when Johnny Long began to collect Google search queries that uncovered vulnerable systems and/or sensitive information disclosures – labeling them googleDorks.[6]

The list of Google Dorks grew into a large dictionary of queries, which were eventually organized into the original Google Hacking Database (GHDB) in 2004.[7][8]

Since its heyday, the concepts explored in Google hacking have been extended to other search engines, such as Bing[9] and Shodan.[10] Automated attack tools[11] use custom search dictionaries to find vulnerable systems and sensitive information disclosures in public systems that have been indexed by search engines.[12]

Protection

Robots.txt is a well known file for search engine optimization and protection against google dorking. It involves use of robots.txt to disallow everything or specific endpoints (hackers can still search robots.txt for endpoints) which prevents google bot from crawling sensitive endpoints such as admin panels. According to RFC 5785, modern practice of placing robots.txt is in /.well_known directory.[13]

References
  1. Term Of The Day: Google Dorking - Business Insider
  2. Google dork query, techtarget.com
  3. https://www.researchgate.net/publication/325763845_Study_on_Implementation_and_Impact_of_Google_Hacking_in_Internet_Security
  4. "Refine web searches - Google Search Help". support.google.com. Retrieved 2020-12-16.
  5. Karch, Marziah. "Allintitle Definition". About.com. About.com. Retrieved 29 February 2020.
  6. "googleDorks created by Johnny Long". Johnny Long. Archived from the original on 8 December 2002. Retrieved 8 December 2002.
  7. "Google Hacking Database (GHDB) in 2004". Johnny Long. Archived from the original on 7 July 2007. Retrieved 5 October 2004.
  8. "Google Hacking for Penetration Testers, Volume 1". Johnny Long. Retrieved 20 February 2005.
  9. "Bing Hacking Database (BHDB) v2". Bishop Fox. Retrieved 27 August 2014.
  10. "Shodan Hacking Database (SHDB) - Part of SearchDiggity tool suite". Bishop Fox. Retrieved 21 June 2013.
  11. "SearchDiggity - Search Engine Attack Tool Suite". Bishop Fox. Retrieved 27 August 2014.
  12. "Google Hacking History". Bishop Fox. Retrieved 27 August 2014.
  13. https://tools.ietf.org/html/rfc5785
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.