Difference between revisions of "Testing: Conduct search engine discovery/reconnaissance for information leakage (OTG-INFO-001)"

From OWASP
Jump to: navigation, search
(Remediation Removed at the Request of Matteo Meucci)
(18 intermediate revisions by 8 users not shown)
Line 1: Line 1:
{{Template:OWASP Testing Guide v3}}
+
{{Template:OWASP Testing Guide v4}}
 
+
'''This is a draft of a section of the new Testing Guide v3'''
+
  
 
== Brief Summary ==
 
== Brief Summary ==
<br>
+
There are direct and indirect elements to Search engine discovery and reconnaissance. Direct methods relate to searching the Google Index and remove the associated web content from the Google Cache. Indirect methods relate to gleaning sensitive design and configuration information by searching forums, newsgroups and tendering websites.
This section describes how to search the Google Index and remove the associated web content from the Google Cache.
+
<br>
+
  
 
== Description of the Issue ==  
 
== Description of the Issue ==  
<br>
+
Once the GoogleBot has completed crawling, it commences indexing the web page based on tags and associated attributes, such as <TITLE>, in order to return the relevant search results. [1]
Once GoogleBot has completed crawling, it commences indexing the web page based on tags and associated attributes, such as <TITLE>, in order to return the relevant search results. [1]
+
  
 
If the robots.txt file is not updated during the lifetime of the web site, then it is possible for web content not intended to be included in Google's Search Results to be returned.
 
If the robots.txt file is not updated during the lifetime of the web site, then it is possible for web content not intended to be included in Google's Search Results to be returned.
  
 
Therefore, it must be removed from the Google Cache.
 
Therefore, it must be removed from the Google Cache.
<br>
 
  
 
== Black Box Testing==
 
== Black Box Testing==
Line 22: Line 16:
 
Google provides the Advanced "cache:" search operator [2], but this is the equivalent to clicking the "Cached" next to each Google Search Result.  Hence, the use of the Advanced "site:" Search Operator and then clicking "Cached" is preferred.
 
Google provides the Advanced "cache:" search operator [2], but this is the equivalent to clicking the "Cached" next to each Google Search Result.  Hence, the use of the Advanced "site:" Search Operator and then clicking "Cached" is preferred.
  
The Google SOAP Search API supports the doGetCachedPage and the associated doGetCachedPageResponse SOAP Messages [3] to assist with retrieving cached pages. An implementation of this is under development by the [http://www.owasp.org/index.php/Category:OWASP_Google_Hacking_Project OWASP "Google Hacking" Project]
+
The Google SOAP Search API supports the doGetCachedPage and the associated doGetCachedPageResponse SOAP Messages [3] to assist with retrieving cached pages. An implementation of this is under development by the [[::Category:OWASP_Google_Hacking_Project |OWASP "Google Hacking" Project]].
  
 
== Example ==
 
== Example ==
Line 29: Line 23:
 
site:owasp.org
 
site:owasp.org
 
</pre>
 
</pre>
[[Image:Google_site_Operator_Search_Results_Example.JPG]]
+
[[Image:Google_site_Operator_Search_Results_Example_20121219.jpg]]
  
 
To display the index.html of owasp.org as cached by Google the following Google Search Query is issued:
 
To display the index.html of owasp.org as cached by Google the following Google Search Query is issued:
Line 35: Line 29:
 
cache:owasp.org
 
cache:owasp.org
 
</pre>
 
</pre>
[[Image:Google_Cached_Example.JPG]]
+
[[Image:Google_cache_Operator_Search_Results_Example_20121219.jpg]]
  
  
  
 
== Gray Box testing and example ==  
 
== Gray Box testing and example ==  
Grey Box testing is the same as Black Box testing above
+
Grey Box testing is the same as Black Box testing above.
  
 
== References ==
 
== References ==
[1] "Google 101: How Google crawls, indexes, and serves the web" - http://www.google.com/support/webmasters/bin/answer.py?answer=70897 <br>
+
'''Web'''<br>
[2] "Advanced Google Search Operators" - http://www.google.com/help/operators.html <br>
+
[1] "Google Basics: Learn how Google Discovers, Crawls, and Serves Web Pages" - http://www.google.com/support/webmasters/bin/answer.py?answer=70897 <br>
[3] "Google SOAP Search API" - http://code.google.com/apis/soapsearch/reference.html#1_2 <br>
+
[2] "Operators and More Search Help" - http://support.google.com/websearch/bin/answer.py?hl=en&answer=136861 <br>
[4] "Preventing content from appearing in Google search results" - http://www.google.com/support/webmasters/bin/topic.py?topic=8459
+
 
 +
'''Tools'''<br>
 +
[1] FoundStone SiteDigger - http://www.mcafee.com/uk/downloads/free-tools/sitedigger.aspx <br>
 +
[2] Google Hacker - http://yehg.net/lab/pr0js/files.php/googlehacker.zip<br>
 +
[3] Stach & Liu's Google Hacking Diggity Project - http://www.stachliu.com/resources/tools/google-hacking-diggity-project/ <br>

Revision as of 20:54, 12 June 2013

This article is part of the new OWASP Testing Guide v4. 
At the moment the project is in the REVIEW phase.

Back to the OWASP Testing Guide v4 ToC: https://www.owasp.org/index.php/OWASP_Testing_Guide_v4_Table_of_Contents Back to the OWASP Testing Guide Project: http://www.owasp.org/index.php/OWASP_Testing_Project

Contents


Brief Summary

There are direct and indirect elements to Search engine discovery and reconnaissance. Direct methods relate to searching the Google Index and remove the associated web content from the Google Cache. Indirect methods relate to gleaning sensitive design and configuration information by searching forums, newsgroups and tendering websites.

Description of the Issue

Once the GoogleBot has completed crawling, it commences indexing the web page based on tags and associated attributes, such as <TITLE>, in order to return the relevant search results. [1]

If the robots.txt file is not updated during the lifetime of the web site, then it is possible for web content not intended to be included in Google's Search Results to be returned.

Therefore, it must be removed from the Google Cache.

Black Box Testing

Using the advanced "site:" search operator, it is possible to restrict Search Results to a specific domain [2].

Google provides the Advanced "cache:" search operator [2], but this is the equivalent to clicking the "Cached" next to each Google Search Result. Hence, the use of the Advanced "site:" Search Operator and then clicking "Cached" is preferred.

The Google SOAP Search API supports the doGetCachedPage and the associated doGetCachedPageResponse SOAP Messages [3] to assist with retrieving cached pages. An implementation of this is under development by the OWASP "Google Hacking" Project.

Example

To find the web content of owasp.org indexed by Google Cache the following Google Search Query is issued:

site:owasp.org

Google site Operator Search Results Example 20121219.jpg

To display the index.html of owasp.org as cached by Google the following Google Search Query is issued:

cache:owasp.org

Google cache Operator Search Results Example 20121219.jpg


Gray Box testing and example

Grey Box testing is the same as Black Box testing above.

References

Web
[1] "Google Basics: Learn how Google Discovers, Crawls, and Serves Web Pages" - http://www.google.com/support/webmasters/bin/answer.py?answer=70897
[2] "Operators and More Search Help" - http://support.google.com/websearch/bin/answer.py?hl=en&answer=136861

Tools
[1] FoundStone SiteDigger - http://www.mcafee.com/uk/downloads/free-tools/sitedigger.aspx
[2] Google Hacker - http://yehg.net/lab/pr0js/files.php/googlehacker.zip
[3] Stach & Liu's Google Hacking Diggity Project - http://www.stachliu.com/resources/tools/google-hacking-diggity-project/