😱 I watched @GodfatherOrwa 's insightful talk "The Power of Shodan - Leveraging Shodan for Critical Vulnerabilities" at @NahamSec 's #NahamCon2023 and have condensed the ~25 minute talk for you to read in 2 minutes.
Here's some interesting bug bounty tips and tricks ⬇️
1. To find all information related to *.target.*, you first need to identify the organization's name. You can do this by clicking the lock icon -> connection is secure -> certificate is valid.
This is wrt Brave/Chrome, there will something similar for those using Firefox.
2. Use this dork to find all information related to *.target.*
3. If you are targeting a specific TLD such as *.target.com, then use this dork as shown below.
4. Hunting on a huge domain will give you loads of results. To filter unnecessary results like say "Invalid URL", use this dork.
5. You can check all http titles and other info related to the target at "Facet Analysis". Say if you've found pages with "302 Found" in title when filtering with http.title and want to look at these IPs only, use this dork.
6. Tip: Sometimes domain names will not be accessible, but their corresponding IPs found in shodan will give you live pages. In such scenarios dork for this domain name in Google, Bing, URLScan, Web Archive and more.
7. If you have got lot of cached entries for the target domain, check manually if some directory is accessible. Try to understand what sort of error you are getting when accessing certain pages and guess the web server used. Then you can do content discovery on the page.
8. As a free user in Shodan, you'll have access to only two pages, hence remember to filter unwanted results and look into the ones you need only. Use the "-" character to filter unwanted results. Look at point 4 for example.
9. You can also use status codes like 302, 200, 403 in the dork to find pages corresponding to that. It's interesting to look at pages with 403.
10. Sometimes you can bypass WAF by accessing the IP of the page rather than the domain name. Once you've an IP without WAF, fuzz intelligently.
11. If you have a windows app domain like IIS Web Server Page, then dork for more results on this domain in Bing for better results.
If you've found this thread informative:
1. Follow me @thebinarybot to see more such quality content in your feed 🚀 2. RT the tweet below to share this thread with your audience - sharing is caring ☘️
1. Error messages: Sometimes error messages can reveal important information about the application's database, such as table names or column names. An attacker can use this information to craft a SQL injection attack.
2. Search fields: Search fields are often overlooked when testing for SQL injection vulnerabilities, but they can be an easy target for attackers. In un-sanitized search queries, an attacker can inject SQL code to retrieve sensitive data from the database.
1. Follow me @thebinarybot to get quality content on cybersecurity and bug bounty hunting. 2. RT the tweet below to share this thread with your audience
Worry no more. Open the thread below and master to core!
🧵👇
1. Pre-requisites
I still believe you can get into Cybersecurity without having little to no technical knowledge. That being said, if you want to master the art I would highly suggest you to learn these topics:
1. Networks 2. Operating Systems 3. Programming - Python/Bash/JS
2. Practice by doing
One of the best ways to learn is to learn by doing. Here's a list of freemium platforms where you can learn hands-on.