> For the complete documentation index, see [llms.txt](https://book.turbosec.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.turbosec.net/all-the-other-layers-recon/web-recon.md). # Web Recon ## Fuzz for backdoors and params ``` wfuzz -u 'http://example.com/index.php?FUZZ=ls' -w /usr/share/seclists/Discovery/Web-Content/burp-parameter-names.txt -H "Cookie: somecookie" ``` ## Find & Enum After [port scanning](/all-the-other-layers-recon/scanning.md) and finding web servers. ### Brute force directories #### Using ffuf ``` ffuf -u http://:/FUZZ -w /usr/share/seclists/Discovery/Web-Content/directory-list-2.3-big.txt -fc 404,400 -of ecsv -o ffufed ``` ## Login & Authentication brute force ### HTTP Basic Authorization Header Brute Force Basic authorization is..**basic**. A username and a password separated by a colon is then encoded in Base64. The screenshot below demonstrate the credentials admin:admin being sent through the Authorization header of an HTTP request. ![](/files/-MkXr148onxpziKddnkj) ``` hydra -l admin -P passwordlist -s -f example.com http-get /api/v1/users -vV -t 64 ``` {% hint style="info" %} **ProTip:** You can/should always test first by using a set of valid credentials and check if it returns it valid. ``` hydra -l known_user -p known_password -s -f example.com http-get /api/v1/users -vV ``` {% endhint %} ### HTTP Post form Brute Force Most of the time, authentication is made via a form posted to the web server. You can try to brute force it but watch out for **CSRF**. Try sending the same request twice using **burp.** ``` hydra -l admin -P /usr/share/wordlists/rockyou.txt -s 31111 -f example.com http-post-f ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://book.turbosec.net/all-the-other-layers-recon/web-recon.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.