Article

Advanced Google Dorking part 3

Date

May 16, 2023

Share

Advanced Google Dorking part 3

Advanced Google Dorking: A Masterclass in Search and Cybersecurity

Google Dorking, often referred to as Google hacking, utilizes the advanced search capabilities of the Google search engine to uncover hidden or sensitive information that is publicly accessible but not meant to be exposed. By leveraging specific search operators, professionals can pinpoint files, configurations, or vulnerabilities indexed by Google. In this blog, we explore Google Dorking from its basics to advanced usage with detailed examples, tools, and ethical considerations.

Introduction

The internet is a vast repository of information, much of which is deliberately shared with the world. However, not all data indexed by search engines like Google is meant to be openly accessible. Misconfigurations, errors, or ignorance can lead to sensitive data being exposed to public scrutiny. Google Dorking is a technique that takes advantage of these oversights. Originally used for benign purposes, such as enhancing search precision, it has evolved into a potent tool in the fields of cybersecurity, penetration testing, and OSINT (Open Source Intelligence).

This blog is your gateway to mastering the art of Google Dorking. Whether you are a cybersecurity professional looking to strengthen your defensive strategies or an ethical hacker aiming to uncover vulnerabilities responsibly, understanding how to wield Google Dorking effectively is essential. Through this guide, we will:

  • Demystify the key search operators that power Google Dorking.
  • Explore advanced techniques with practical examples.
  • Highlight the tools that enhance its efficiency.
  • Discuss how to defend against Google Dorking as an organization.

As you delve into the following sections, remember that with great power comes great responsibility. Ethical considerations must always be at the forefront of your efforts, ensuring this knowledge is used constructively and within the bounds of the law.

1️⃣ Open Jenkins Instances

intitle:"Dashboard [Jenkins]" Credentials

2️⃣ Atlassian Confluence Dashboard

#related CVE: CVE-2019-3396
intitle:dashboard-confluence


inurl:http://confluence. login.action
inurl:https://wiki. .com/confluence/
allinurl: /confluence/login.action?
"/spacedirectory/view.action"
"/pages/viewpage.action?"
"/pages/releaseview.action?"
"aboutconfluencepage.action"

3️⃣ phpMyAdmin

inurl:main ext:php "Welcome to phpMyAdmin" "running on"
"Welcome to phpMyAdmin" "running on" inurl:main.php
inurl:main.php phpMyAdmin
inurl:main.php "Welcome to phpMyAdmin"
inurl:sql.php "phpmyadmin"
inurl:sql "phpmyadmin"

4️⃣ AWS S3 BUCKET

site:*.s3.amazonaws.com
site:*.*.s3.amazonaws.com
site:*.*.*.s3.amazonaws.com
inurl:"s3.amazonaws.com"

site:*.s3.amazonaws.com intitle:Bucket loading


#here we are matching keywords in domain,title and url
#also view the page source for hidden cloud assets in all subdomains, IPs, vhosts and much more deep stuff.

5️⃣ KIBANA DASHBOARD

inurl:kibana inurl:app
inurl:kibana inurl:app inurl:5601

#default port 5601, similarly make shodan dork for it as well