Jump to content

Google hacking: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
VRVFR
Tags: blanking repeating characters Possible vandalism
m Reverted edits by 99.121.3.24 (talk) (HG) (3.4.6)
Line 1: Line 1:
{{pp-pc1|expiry=March 2, 2019}}
EEE
{{pp-pc}}
FGBVDFSVBHNXCBHJGNYT RFVN,BJKV ,MNJBVHCNV JCH,FVBMGVRMFVB VJFMGJRTN BCVFM GJF VGJMDKC, NVCDSFGCJDKERSX,BHJMHCNSBXV BHN BJMN BC MBVNMVBBNMCVHJGBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBAn automated filter has identified this edit as potentially unconstructive, so it has been disallowed. Please do not remove all the text of Wikipedia pages. The resulting blank pages are harmful to Wikipedia because they confuse readers.
{{distinguish|Google Hacks}}
If you would like to experiment, please use the sandbox. If this edit is constructive, please report this error.
'''Google hacking''', also named '''Google dorking''',<ref>[http://www.businessinsider.com/term-of-the-day-google-dorking-2014-8 Term Of The Day: Google Dorking - Business Insider]</ref><ref>[http://whatis.techtarget.com/definition/Google-dork-query Google dork query], techtarget.com</ref> is a [[Hacker (computer security)|computer hacking]] technique that uses [[Google Search]] and other [[Google]] applications to find security holes in the [[computer configuration|configuration]] and [[source code|computer code]] that [[website]]s use.


== Basics ==
If this page is duplicate of another, please redirect it to an appropriate existing page.

If this page has been vandalised, please revert it to the last legitimate version.
Google hacking involves using advanced operators in the Google [[Web search engine|search engine]] to locate specific strings of text within search results. Some of the more popular examples are finding specific versions of vulnerable [[Web application]]s. A search query with <code>intitle: admbook intitle: Fversion filetype: php</code> would locate all web pages that have that particular text contained within them. It is normal for [[default (computer science)|default]] installations of applications to include their running version in every page they serve, for example, "Powered by XOOPS 2.2.3 Final".
If you feel that the content of this page is inappropriate, please edit the page and replace it with appropriate content or leave a message on the talk page.

If you believe this page should be deleted altogether, please see articles for deletion for information on how to proceed.
One can even retrieve the username and password list from [[Microsoft FrontPage]] servers by inputting the given microscript in Google search field:
If this page is a biography of a living person that is problematic, please report the problem at the noticeboard.

If you have any questions, you can ask for assistance at the Help Desk.
"#-Frontpage-" inurl: administrators.pwd
BBBBBBBBBBBBBBBBBBBB
or filetype: log inurl password login
Warning: An automated filter has identified this edit as removing a large amount of content. While some material on Wikipedia should be removed, such as vandalism and false or libelous information, we discourage removal of content without a valid reason. If you believe that your removal is constructive, please go to the bottom of this page and press 'Publish changes' to continue (be sure to enter an edit summary if you have not done so already). If you did not remove a large amount of content, and you believe that this edit is constructive, please report this error.

Your action has triggered the Edit Filter Warning: An automated filter has detected a repeated sequence of characters in this edit. This is often an indicator of vandalism. If the edit is constructive, please go to the bottom of this page and press 'Publish changes' to continue. Otherwise, if your edit is clearly vandalism, you may be blocked from editing Wikipedia. If you are unsure of where the repeated sequence of characters occurs, and this message is in error, please report this.
Devices connected to the Internet can be found. A search string such as <code>inurl: "ViewerFrame?Mode="</code> will find public web cameras.
Your action has triggered the Edit Filter An automated filter has identified this edit as potentially unconstructive, so it has been disallowed. If this edit is constructive, please report this error. Disruptive editing may result in a block from editing.

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

==Advanced operators==
There are many similar advanced operators which can be used to exploit insecure websites:

{| class="wikitable"
|-
! Operator!! Purpose!! Mixes with Other Operators?!! Can be used Alone?!! Web!! Images!! Groups!! News
|-
| intitle||Search page Title||yes||yes||yes||yes||yes||yes
|-
| allintitle<ref>{{cite web|last1=Karch|first1=Marziah|title=Allintitle Definition|url=http://google.about.com/od/a/g/allintitledef.htm|website=About.com|publisher=About.com|accessdate=6 September 2015}}</ref>||Search page title||no||yes||yes||yes||yes||yes
|-
| inurl||Search URL||yes||yes||yes||yes||not really||like intitle
|-
| allinurl||Search URL||no||yes||yes||yes||yes||like intitle
|-
| filetype||specific files||yes|yes|yes||yes||no||not really
|-
| intext||Search text of page only||yes||yes||yes||yes||yes||yes
|-
| allintext||Search text of page only|| really||yes||yes||yes||yes||yes
|-
| site||Search specific site||yes||yes||yes||yes||no||not really
|-
| link||Search for links to pages||yes||yes||yes||no||no||not really
|-
| inanchor||Search link anchor text||yes||yes||yes||yes||not really||yes
|-
| numrange||Locate number||yes||yes||yes||yes||yes||not really
|-
| daterange||Search in date range||yes||yes||yes||not really||not really||not really
|-
| author||Group author search||yes||yes||no||no||yes||not really
|-
| group||Group name search|| really||yes||no||yes||yes||not really
|-
| insubject||Group subject search||yes||yes||like intitle||like intitle||yes||like intitle
|-
| msgid||Group msgid search||no
||yes||not really||not really||yes|yes really
|}

The "link:" search operator that Google used to have, has been turned off by now (2017).<ref>{{Cite news|url=https://twitter.com/JohnMu/status/819209116694548480|title=John Mueller, Webmaster Trends Analyst at Google|newspaper=Twitter|language=en|access-date=2017-01-28}}</ref>

==History of Google Hacking==
{{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 [[Vulnerability (computing)|vulnerable systems]] and/or [[Data breach|sensitive information disclosures]] - labeling them googleDorks.<ref name=googleDorks2002>{{cite web|url=http://johnny.ihackstuff.com/security/googleDorks.shtml |title=googleDorks created by Johnny Long |publisher=Johnny Long |accessdate=8 December 2002 |deadurl=yes |archiveurl=https://web.archive.org/web/20021208144443/http://johnny.ihackstuff.com/security/googleDorks.shtml |archivedate=8 December 2002 |df= }}</ref>

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.<ref name=ghdb2004>{{cite web|url=http://johnny.ihackstuff.com/blog/my-blog-like-thing/google-hacking-database.html |title=Google Hacking Database (GHDB) in 2004 |publisher=Johnny Long |accessdate=5 October 2004 |deadurl=yes |archiveurl=https://web.archive.org/web/20070707185932/http://johnny.ihackstuff.com/blog/my-blog-like-thing/google-hacking-database.html |archivedate=7 July 2007 |df= }}</ref><ref name=ghbook2005>{{cite web |url=https://www.amazon.com/Google-Hacking-Penetration-Testers-1/dp/1931836361 |title=Google Hacking for Penetration Testers, Volume 1 |publisher=Johnny Long |accessdate=20 February 2005 }}</ref>

Since its heyday, the concepts explored in Google Hacking have been extended to other [[search engines]], such as [[Bing (search engine)|Bing]]<ref name=bingHackingBF>{{cite web |url=http://www.bishopfox.com/resources/tools/google-hacking-diggity/attack-tools/#bing-hacking-database---bhdb-v2 |title=Bing Hacking Database (BHDB) v2 |publisher=Bishop Fox |accessdate=27 August 2014 }}</ref> and [[Shodan (website)#Automated Search Tools|Shodan]].<ref name=shodanHackingDB>{{cite web |url=http://www.bishopfox.com/resources/tools/google-hacking-diggity/attack-tools/#shodan-hacking-database---shdb |title=Shodan Hacking Database (SHDB) - Part of SearchDiggity tool suite |publisher=Bishop Fox |accessdate=21 June 2013 }}</ref> Automated attack tools<ref name=searchDiggityBF>{{cite web |url=http://www.bishopfox.com/resources/tools/google-hacking-diggity/attack-tools/#searchdiggity |title=SearchDiggity - Search Engine Attack Tool Suite |publisher=Bishop Fox |accessdate=27 August 2014 }}</ref> use custom search dictionaries to find [[vulnerability (computing)|vulnerable systems]] and [[data breach|sensitive information disclosures]] in public systems that have been indexed by search engines.<ref name="ghHistoryBF">{{cite web |url=http://www.bishopfox.com/resources/tools/google-hacking-diggity/google-hacking-history/ |title=Google Hacking History |publisher=Bishop Fox |accessdate=27 August 2014 }}</ref>

==References==
{{Reflist}}

== External links ==
* [http://www.bishopfox.com/resources/tools/google-hacking-diggity/ Google Hacking Diggity Project - Bishop Fox] – a research and development initiative dedicated to investigating the latest techniques that leverage search engines (such as Google, Bing, and Shodan) to quickly identify vulnerable systems and sensitive data on public networks. An arsenal of free attack and defense tools related to search engine hacking are available for download.
* [http://www.exploit-db.com/google-hacking-database-reborn/ Google Hacking Database (GHDB) - REBORN - 09Nov2010] – Exploit-db.com folks picked up the effort of maintaining and adding to the original GHDB JohnnyIHackStuff.com created by Johnny Long.
* [http://www.boris-koch.de/wp-content/uploads/2011/01/Liste-Google-Hacking.pdf "Google Hacking: .pdf Document"], ''boris-koch.de'' (printable, .pdf)
* [http://www.trickspack.com/google-dorks-list/ "Google Hacking: .pdf Document"], ''boris-koch.de'' (printable, .pdf)

* [https://www.google.com/help/cheatsheet.html "Google Help: Cheat Sheet"], ''Google'' (printable)
* [https://www.blackhat.com/presentations/bh-europe-05/BH_EU_05-Long.pdf Google Hacking for Penetration] - Using Google as a Security Testing Tool, Introduction by Johnny Long

{{Google Inc.}}
[[Category:Computer security procedures]]
[[Category:Google Search|hacking]]

Revision as of 15:08, 15 March 2019

Google hacking, also named Google dorking,[1][2] is a computer hacking technique that uses Google Search and other Google applications to find security holes in the configuration and computer code that websites use.

Basics

Google hacking involves using advanced operators in the Google search engine to locate specific strings 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".

One can even retrieve the username and password list from Microsoft FrontPage servers by inputting the given microscript in Google search field:

"#-Frontpage-" inurl: administrators.pwd
or filetype: log inurl password login

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 servers.

Advanced operators

There are many similar advanced operators which can be used to exploit insecure websites:

Operator Purpose Mixes with Other Operators? Can be used Alone? Web Images Groups News
intitle Search page Title yes yes yes yes yes yes
allintitle[3] Search page title no yes yes yes yes yes
inurl Search URL yes yes yes yes not really like intitle
allinurl Search URL no yes yes yes yes like intitle
filetype specific files yes|yes yes no not really
intext Search text of page only yes yes yes yes yes yes
allintext Search text of page only really yes yes yes yes yes
site Search specific site yes yes yes yes no not really
link Search for links to pages yes yes yes no no not really
inanchor Search link anchor text yes yes yes yes not really yes
numrange Locate number yes yes yes yes yes not really
daterange Search in date range yes yes yes not really not really not really
author Group author search yes yes no no yes not really
group Group name search really yes no yes yes not really
insubject Group subject search yes yes like intitle like intitle yes like intitle
msgid Group msgid search no yes not really not really yes really

The "link:" search operator that Google used to have, has been turned off by now (2017).[4]

History of 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.[5]

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.[6][7]

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

References

  1. ^ Term Of The Day: Google Dorking - Business Insider
  2. ^ Google dork query, techtarget.com
  3. ^ Karch, Marziah. "Allintitle Definition". About.com. About.com. Retrieved 6 September 2015.
  4. ^ "John Mueller, Webmaster Trends Analyst at Google". Twitter. Retrieved 2017-01-28.
  5. ^ "googleDorks created by Johnny Long". Johnny Long. Archived from the original on 8 December 2002. Retrieved 8 December 2002. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  6. ^ "Google Hacking Database (GHDB) in 2004". Johnny Long. Archived from the original on 7 July 2007. Retrieved 5 October 2004. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  7. ^ "Google Hacking for Penetration Testers, Volume 1". Johnny Long. Retrieved 20 February 2005.
  8. ^ "Bing Hacking Database (BHDB) v2". Bishop Fox. Retrieved 27 August 2014.
  9. ^ "Shodan Hacking Database (SHDB) - Part of SearchDiggity tool suite". Bishop Fox. Retrieved 21 June 2013.
  10. ^ "SearchDiggity - Search Engine Attack Tool Suite". Bishop Fox. Retrieved 27 August 2014.
  11. ^ "Google Hacking History". Bishop Fox. Retrieved 27 August 2014.