Recon, the gathering of information about your target, is becoming more and more important! π§
Here are the tools to help you spot subdomains, vhosts, S3 buckets, parameters and more faster and more effective than the others π
[1οΈβ£] DNS
This DNS toolkit by @pdiscoveryio can do a lot! But let's focus on reverse DNS lookups π
Often, you have a huge list of IP addresses π
Just like resolving a domain to an IP, you can also try doing the opposite using PTR records!
Et voila! Domains to continue recon! π
[2οΈβ£] Amass
This network mapping tool by @owasp is incredible, but let's hone in on doing subdomain enumeration. πΈ
The main domains companies use are often well-secured. But what about the domain that nobody knows about? Those can be riddled with bugs! π
Let's find them! π
[3οΈβ£] @nmap
Nmap stands for "Network Mapper" and that's precisely what it does.
This 25-year-old tool is FAR from outdated!
Let's use Nmap to find out what's actually running on those endless machines you've enumerated so far! π
[4οΈβ£] VHostScan
This Python scanner by @codingo_ is an excellent tool for finding virtual hosts! π¨βπ»
What's that? Unlike subdomains, vhosts allow multiple applications to be hosted on a single server. π₯
This slightly esoteric feature means not many hunters are looking for this! π
[5οΈβ£] Httprobe
All this recon has given us many subdomains, but what now? π€·ββοΈ
This tool by @TomNomNom will help us find all the web servers running on these subdomains! π
[6οΈβ£] Waybackurls
Another tool by @TomNomNom can help us continue.
Instead of opting for active directory fuzzing, let's use the power of history to see what we can find on a target's website!
This tool uses the @waybackmachine to find new endpoints passively! π
[7οΈβ£] S3enum
This Go tool by @koenrh automates AWS S3 bucket enumeration.
Using this tool, you may be able to find the next big misconfiguration or overly permissive S3 bucket! π
[8οΈβ£] EyeWitness
If you're overwhelmed with endpoints, that's okay!
Let's bring some order to this madness using this tool by @FortyNorthSec πͺ
It allows you to organize endpoints depending on their return value quickly. Screenshots of the page are a bonus! πΌ
[9οΈβ£] Relative URL extractor
JavaScript files are recon goldmines! They sometimes reference very interesting relative URLs that you need to know about! π§
But manually going through 1000s of JS files, no! πͺ
Use this great tool by @jobertabma π
[1οΈβ£0οΈβ£] TruffleHog
If you're lucky, you may have found a git repository during your recon! π
Let's use this tool by @trufflesec to dig into it and uncover all secrets the repo has to hold! π
[1οΈβ£1οΈβ£] Arjun
Let's talk about enumerating GET parameters!
If you were thinking of brute-forcing thousands of them, then check out Arjun by @s0md3v π
It can check for thousands of GET params in under 50 requests! π€―
[1οΈβ£2οΈβ£] Wappalyzer
One last trick we'll give you is fingerprinting everything you find using @Wappalyzer π
This way, you know what you're dealing with and what exploit might or might not work! πͺ
π§΅ And that's a wrap!
Note that there are alternatives to the tools we've showcased here, and looking around for something you like is highly recommended! π
Be sure to like this tweet and follow @intigriti if you want more of these threads! π
List of most loved open-source web hacking tools we featured on Intigriti! π€
A thread! π§΅π
1οΈβ£ Malicious PDF Generator
Malicious PDF Generator is an open-source toolkit that lets you generate tens of malicious PDF files to exploit various vulnerabilities and insecure features in PDF readers! π€
Hakoriginfinder by @hakluke is a simple tool to quickly identify the origin hosts of targets behind Cloudflare, AWS, and other types of reverse proxies! π€
Most hackers limit themselves to only using proxy interceptor, repeater, and intruder... π€
But these 8 unpopular Burp Suite features can save you hours of testing time (and find you more vulnerabilities)! π€
A thread! π§΅π
1οΈβ£ Macros
Burp Suite provides built-in macro support that helps automate repetitive tasks such as refreshing authentication tokens and retrieving anti-CSRF tokens for each new request.
For instance, if you're testing an application that revokes anti-CSRF tokens with each new HTTP request, you can quickly set up a macro to automatically obtain a new CSRF token before sending a new request in Repeater or Intruder, preventing you from having to manually update the token every time.
2οΈβ£ Match & replace Rules
Burp Suite's Match & Replace feature allows you to automatically modify any intercepted HTTP requests and responses, eliminating the need to manually edit each request when testing specific payloads or bypassing certain security controls.
Do you want to find more vulnerabilities with recon? π€
Open this thread (step-by-step guide)! π§΅ π
Before we dive in, let's first cover what recon (short for 'reconnaissance') is.
Recon is the first crucial phase of any engagement and it involves mapping out (sub)domains, IP ranges, technologies and services, as well as any other publicly accessible information through several techniques
Bug bounty hunters who spend time performing reconnaissance, are almost always rewarded well for their efforts as they often come across exposed assets or hosts that have never been tested before π€
Let's now dive deeper into how you can find these untested assets to find more vulnerabilities! π
12 API hacking bug bounty tips you must try on your target! π
π§΅ π
1οΈβ£ Blind XSS via request headers
Applications log your data in various ways, including in insecure ways. Always test for blind XSS vulnerabilities by injecting your payload in common request headers, such as:
β’ Referrer
β’ X-Forwarded-For, X-Forwarded-Host, X-Forwarded-Ip, Host (in case of a reverse proxy)
β’ User-Agent
β’ Etc.
Are your request paths prefixed with an "/api/v2"? Try testing legacy endpoints by:
β’ Replacing "/api/v2" with "/api/v1"
β’ Removing "/v2" altogether
Try similarly in case it's a subdomain: api-v2\.example\.com β api-v1\.example\.com or api\.example\.com
XML eXternal Entity (XXE) injection is a vulnerability class that stems from inadequate user input validation during XML parsing, allowing attackers to take advantage of parser misconfigurations!
This often leads to local file read, server-side request forgery, and, in severe cases, even remote code execution!
However, XXE vulnerabilities are much harder to spot nowadays.
You must pay close attention to application components that might accept and process XML data, such as:
β’ Document converters (Word/Excel)
β’ SVG file processors
β’ RSS/Atom feed processors
β’ Importing features (accepting XML data)