<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Burp Suite on Jhuk Tech News</title><link>https://jhuk.tech/categories/burp-suite/</link><description>Recent content in Burp Suite on Jhuk Tech News</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 25 Jul 2023 20:08:52 +0000</lastBuildDate><atom:link href="https://jhuk.tech/categories/burp-suite/index.xml" rel="self" type="application/rss+xml"/><item><title>Fuzzing Forms-Based Authentication Reveals Working Username and Password</title><link>https://jhuk.tech/2023/07/25/fuzzing-forms-based-authentication-reveals-working-username-and-password/</link><pubDate>Tue, 25 Jul 2023 20:08:52 +0000</pubDate><guid>https://jhuk.tech/2023/07/25/fuzzing-forms-based-authentication-reveals-working-username-and-password/</guid><description>&lt;p&gt;In this lab exploring HTML forms-based authentication, I use Burp Suite to fuzz a username of interest to discover a valid password combination. &amp;ldquo;Fuzzing&amp;rdquo; in the context of web application security means any automated attempt to inject a large number variables into any field that accepts user input. The tester then monitors the application for unexpected behavior or unusual results that may indicate the presence of a vulnerability. Possibilities for fuzzing input ranges from common usernames, passwords, URLs, sensitive data patterns, executable shell commands and SQLi payloads. &lt;a href="https://github.com/danielmiessler/SecLists" target="_blank" rel="noreferrer"&gt;SecLists is a well-known repository&lt;/a&gt; that maintains wordlists for each of these mentioned categories. The choice of which wordlist to use depends on the context of the input field and what category of vulnerability the tester suspects may exist within the application.&lt;/p&gt;</description></item></channel></rss>