<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Muhammad Abdullah Niazi on Medium]]></title>
        <description><![CDATA[Stories by Muhammad Abdullah Niazi on Medium]]></description>
        <link>https://medium.com/@NiaziSec?source=rss-171b87d2579------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*BdjGIN56aSSFYW-NTDWhHA.jpeg</url>
            <title>Stories by Muhammad Abdullah Niazi on Medium</title>
            <link>https://medium.com/@NiaziSec?source=rss-171b87d2579------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 04:32:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@NiaziSec/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to Start a Career as an IT Business Analyst]]></title>
            <link>https://medium.com/@NiaziSec/how-to-start-a-career-as-an-it-business-analyst-32eb6a269e6b?source=rss-171b87d2579------2</link>
            <guid isPermaLink="false">https://medium.com/p/32eb6a269e6b</guid>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[it-business-analyst]]></category>
            <category><![CDATA[sdlc-methodologies]]></category>
            <category><![CDATA[waterfall-model]]></category>
            <dc:creator><![CDATA[Muhammad Abdullah Niazi]]></dc:creator>
            <pubDate>Mon, 25 May 2026 04:58:52 GMT</pubDate>
            <atom:updated>2026-08-10T08:14:37.628Z</atom:updated>
            <content:encoded><![CDATA[<h4>Insights about my internship</h4><p>The most common definition of a Business Analyst (Change Champion) is someone who performs business analysis. This is a process of understanding problems, identifying business needs, and helping companies move toward better solutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*baI25bK6Cvasw47trELi1A.png" /></figure><p>A Business Analyst helps organizations implement change. Every change begins with a goal. A company may want to improve customer experience, automate manual work, reduce costs, or launch a new digital product. The Business Analyst helps define how to move from the current state to the desired future state.</p><p>Imagine you are at point A and want to reach point B. Before moving forward, you need to understand:</p><ul><li>Why is point B important?</li><li>What problems exist today?</li><li>What resources are available?</li><li>What risks may appear during the journey.</li></ul><p>For example, if your friend Lucy wants a backpack for her birthday, you would not buy the first one you see. You would ask questions:</p><ul><li>Is the backpack for travel or daily use?</li><li>How much weight will she carry?</li><li>What size and material does she prefer?</li></ul><p>By asking these questions, you identify requirements before making a decision. Business Analysts follow the same approach when building software products and business solutions.</p><h4>Their main responsibility is to understand business needs and translate them into clear requirements.</h4><p>For example, a company may want to automate financial reports that are currently prepared manually. The Business Analyst must:</p><ul><li>Understand what information should appear in the reports</li><li>Identify where the data comes from</li><li>Determine who will use the reports</li><li>Understand how frequently the reports are needed</li></ul><p>Since one person rarely has all the answers, the Business Analyst works with different stakeholders, gathers information, documents requirements, and communicates them to the development team. Because of this, Business Analysts are often called the communication bridge between business representatives and software engineers.</p><p>Skills You Need to: Communication is one of the most important skills for a Business Analyst. A BA spends a large amount of time:</p><ul><li>Talking to stakeholders</li><li>Running meetings</li><li>Asking questions</li><li>Writing documentation</li><li>Explaining requirements to developers</li></ul><p>A Business Analyst does not need to be a software developer, but understanding technical concepts is very helpful.</p><ul><li>APIs</li><li>Databases</li><li>Data structures</li><li>File formats</li><li>ETL processes</li><li>Software architecture</li><li>Release processes</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*XfN92CvWEDmjrWZMrDo_Rw.png" /><figcaption>The tools that most IT business Analyst used are</figcaption></figure><h4>Jira</h4><ul><li>Managing tasks</li><li>Tracking project progress</li><li>Writing user stories</li><li>Managing Agile projects</li></ul><h4>Confluence</h4><ul><li>Writing documentation</li><li>Sharing project knowledge</li><li>Creating requirements documents</li></ul><h4>Microsoft Visio</h4><ul><li>Process diagrams</li><li>Workflow visualization</li><li>Business process mapping</li></ul><h4>Draw.io</h4><ul><li>Flowcharts</li><li>UML diagrams</li><li>BPMN diagrams</li></ul><h4>Miro</h4><ul><li>Brainstorming sessions</li><li>Workshops</li><li>Process mapping</li><li>Team collaboration</li></ul><p>SQL, Excel, Power BI, Python, R</p><p>SQL is especially important because many Business Analysts need to work with databases and analyze stored information.</p><h3>Modeling Techniques Every BA Should Learn</h3><p>Modeling techniques help visualize systems and business processes.</p><p>Important modeling standards include:</p><ul><li>UML (Unified Modeling Language)</li><li>BPMN (Business Process Model and Notation)</li><li>Wireframing and prototyping</li></ul><p>Modern digital products include many advanced features such as:</p><ul><li>Barcode scanning</li><li>Augmented reality</li><li>Location-based services</li><li>Fingerprint authentication</li><li>Facial recognition</li></ul><p>Business Analysts help define how these features should work and how they provide value to users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*tOIkX_3O8hK-E0illv8iuQ.png" /><figcaption>Product Development Lifecycle</figcaption></figure><ol><li>Generating product ideas and researching customer needs.</li><li>Analyzing competitors, market demand, and business value.</li><li>Defining requirements, timelines, and project scope.</li><li>Creating user flows, interfaces, and architecture.</li><li>Building and testing the software product.</li><li>Launching the product to customers.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*btmdKd5rqYyzO4bbYaEIEw.png" /><figcaption>Software Development Lifecycle</figcaption></figure><ol><li>Gathering business needs and defining project goals.</li><li>Estimating costs, resources, and risks.</li><li>Creating architecture and prototypes.</li><li>Developing the application.</li><li>Testing software quality.</li><li>Releasing the product to production.</li><li>Improving and supporting the product after release.</li></ol><h3>Traditional vs Agile Methodologies</h3><p>Traditional approaches like the Waterfall model follow a sequential process where each stage must be completed before the next one begins. Other traditional methodologies include:</p><ul><li>Rational Unified Process (RUP)</li><li>V-Model</li></ul><p>The main disadvantage is that customers usually see the product only at the end of development.</p><h4>Agile focuses on:</h4><ul><li>Flexibility, Iterative development, Fast feedback, Adaptation to changes</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*pGLcbzVmpC3E6zoWXF7xeg.png" /><figcaption>Agile Framework</figcaption></figure><p>Agile teams deliver software in smaller pieces and improve the product continuously.</p><p>Scrum is an <strong>iterative</strong> and <strong>incremental </strong>software development framework that is based on Agile values and principles. Team delivers working product pieces (called <strong>product increments</strong>) in order of priority and value set</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*Zi1gaETe7cwKXp8vYk7J1A.png" /><figcaption>Key concepts include:</figcaption></figure><ul><li>Sprints, Product increments, Daily stand-up meetings, Sprint planning, Sprint reviews</li><li>Scrum is divided into time-boxed iterations, called <strong>sprints</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*oA62UobYeVXZh8ovhRUxpA.png" /><figcaption><strong>sprints</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*d00W4z7T38umVO4pDphbrw.png" /><figcaption>Daily Review</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*q2TTOXOEbRErfi48eUWgJw.png" /><figcaption>Roles</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*5GhIggp85Bf8KbdtcFCbJQ.png" /><figcaption>Timelines</figcaption></figure><h4>Burndown Chart</h4><p>A burndown chart shows how much work remains during a sprint and helps track development progress.</p><p>If you do not have experience yet, you can:</p><ul><li>Create sample BA documents</li><li>Analyze existing applications</li><li>Practice writing user stories</li><li>Create process diagrams</li><li>Work on freelance or internship projects</li></ul><h4>Final Thoughts</h4><p>Every role has demand if you are clear and consistent.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=32eb6a269e6b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bypassing Client-Side Controls]]></title>
            <link>https://medium.com/@NiaziSec/bypassing-client-side-controls-6f85c97747d7?source=rss-171b87d2579------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f85c97747d7</guid>
            <category><![CDATA[bug-bounty-program]]></category>
            <category><![CDATA[bug-bounty-hunter]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[web-testing]]></category>
            <dc:creator><![CDATA[Muhammad Abdullah Niazi]]></dc:creator>
            <pubDate>Tue, 04 Mar 2025 08:16:27 GMT</pubDate>
            <atom:updated>2025-03-04T08:16:27.342Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Web Application Hacker’s Handbook</h4><p>Web applications in the present age widely utilize client-side controls to control user input and optimize performance. The controls function in a user-controlled environment, making them vulnerable to attacks. Within this post, we will analyze the entire client-side data transmission process in detail while examining client-side vulnerabilities alongside attacker methods to circumvent them. A detailed pattern composed this structure, which includes reference page numbers that duplicate the original document’s layout.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Qv9Ny0khH-TEU_f9" /><figcaption><a href="https://github.com/NUSGreyhats/lrn2lrn/blob/master/lessons/hengyeow-yoshi_1_web/lessons/bypassing_client_side_controls/lessonplan.md">https://github.com/NUSGreyhats/lrn2lrn/blob/master/lessons/hengyeow-yoshi_1_web/lessons/bypassing_client_side_controls/lessonplan.md</a></figcaption></figure><h4>Insecure Data Transmission via Client-Side Mechanisms</h4><ul><li><strong>Hidden Form Fields: </strong>Use tools like OWASP ZAP or mitmproxy to intercept and modify requests dynamically. Advanced attackers may encode payloads (e.g., Base64, URL encoding) to bypass basic filters. For ASP.NET applications, check for __VIEWSTATE tampering opportunities if MAC validation is disabled.</li><li><strong>HTTP Cookies: </strong>Retail applications provide users the ability to make arbitrary product purchases through their systems. HTTP Cookies store sensitive data such as DiscountAgreed=25 and accept it without validating it from the server. Attackers can manipulate Modify cookie values through both proxies as well as browser development tools. Exploit misconfigured cookie attributes (e.g., missing HttpOnly, Secure, or SameSite). The vulnerabilities result in either unauthorized discounting opportunities or privileged system access.</li><li><strong>URL Paramete</strong>rs: URL Parameters contain confidential information which threat actors can exploit using browser modification or proxy tools and through direct address modifications. For example, applying pricecode=32. Users can bypass quantity restrictions by changing the code from quantity=1 to quantity=1000.</li><li><strong>Referer Header Abuse: </strong>Use curl with custom headers (-H &quot;Referer: https://legitimate-site.com&quot;) to spoof trusted sources. Test for Referer-based CSRF bypasses by stripping headers entirely.</li></ul><h4>Client-Side Validation Bypass</h4><ul><li><strong>JavaScript Validation: </strong>JavaScript Validation works through client-side scripts (ValidateForm()) which perform input rules checking (numeric quantities and length limits). However, attackers can disable JavaScript to avoid these checks. The attacker intercepts form submissions to modify them by adding quantity=999 into the request. The modification of JavaScript functions with proxies or through browser developer tools by changing return false statements into return true will result in SQL injection or XSS or command injection vulnerabilities when server-side checks are absent.</li><li><strong>Disabled Form Elements: </strong>Use JavaScript injection (e.g., document.getElementById(&#39;adminField&#39;).disabled = false) or DOM XSS to re-enable fields. Test for hidden inputs in React/Angular apps using ReactDOM or ng.probe to manipulate component states.</li></ul><h4>Opaque Data &amp; Obfuscation Bypass</h4><ul><li><strong>ViewState (ASP.NET): </strong>The ASP.NET ViewState uses the __VIEWSTATE hidden field for sensitive data storage without providing MAC security protection. Users who want to exploit Base64-encoded ViewState data should use Decode Base64 utilities like Burp Suite’s ViewState parser. Recode data items (such as price rates) when protection systems disable MAC validation. Impact: Data tampering, price spoofing.</li><li><strong>Encrypted/Obfuscated Parameters: </strong>The system encrypts data through obfuscation with a pad function, yet it does not implement necessary integrity protection measures. The attack method for exploitation involves removing encryption from lower-priced products through the retrieval of secret data points (e.g., pricing_token from budget items). You can find encryption logic by using tools like Jad decompiler for Java alongside .NET Reflector for Silverlight. Users who bypass payment gates and gain entry to premium content features are possible when protection features are disabled.</li></ul><h4>Browser Extension &amp; Native Code Attacks</h4><ul><li><strong>Java Applets/Silverlight/Flash: </strong>Custom browser extensions (e.g., Java applets) perform validation but lack server-side checks. To exploit, Decompile bytecode (e.g., .jar, .xap, .swf) to reverse-engineer validation logic. Modify source code to remove validation (e.g., remove if(i &gt; 50) checks) and recompile. Tools to perform such attacks are Jad (Java), Flasm (Flash), .NET Reflector (Silverlight). The impacts are unauthorized data submission (e.g., SQLi/XXE in “validated” inputs).</li><li><strong>Native Client Components (e.g., ActiveX): </strong>Native code (e.g., ActiveX controls) bypasses browser sandboxes but is vulnerable to reverse engineering. To exploit, use debuggers like OllyDbg or IDA Pro to patch executables or hook into runtime processes. The impacts are privilege escalation, data exfiltration, or code execution.</li></ul><h4>Common Attack Methods</h4><ul><li><strong>Burp Suite Automation: </strong>Use Burp Extensions like Autorize for auth bypass testing or Logger++ to track parameter tampering. Configure Match/Replace Rules to auto-modify headers (e.g., Referer: admin-panel).</li><li><strong>Replay Attacks:</strong> Use Token Replay in Postman by capturing JWTs/encrypted tokens and replaying them in high-privilege contexts. Test for token sidejacking via insecure cookies (e.g., missing Secure flag).</li></ul><h4>Server-Side Mitigations</h4><ul><li><strong>Validation:</strong> Implement positive validation (whitelisting) and schema enforcement (e.g., JSON Schema). Use OWASP ESAPI for input sanitization and libinjection for SQLi detection.</li><li><strong>Data Integrity:</strong> Secure ViewState with enableViewStateMac=&quot;true&quot; and validation=&quot;SHA1&quot;. Use HMAC-SHA256 for token signing and rotate keys regularly. For encrypted parameters, adopt AEAD ciphers (e.g., AES-GCM) to prevent tampering.</li><li><strong>Secure Storage:</strong> Store sensitive data in server-side sessions (e.g., Redis) instead of client-side tokens. Implement rate limiting and CAPTCHA to block brute-force attacks on pricing tokens.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f85c97747d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cracking Linux Password Hashes]]></title>
            <link>https://infosecwriteups.com/cracking-linux-password-hashes-12dfb9e1dc2f?source=rss-171b87d2579------2</link>
            <guid isPermaLink="false">https://medium.com/p/12dfb9e1dc2f</guid>
            <category><![CDATA[kali-linux-tips]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[kali-linux]]></category>
            <category><![CDATA[hashcat]]></category>
            <category><![CDATA[john-the-ripper]]></category>
            <dc:creator><![CDATA[Muhammad Abdullah Niazi]]></dc:creator>
            <pubDate>Fri, 28 Feb 2025 03:55:49 GMT</pubDate>
            <atom:updated>2025-02-28T03:55:49.451Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Comprehensive Guide to John the Ripper, Hashcat, and Other Tools</h4><p>Knowledge of password storage methods alongside hashing techniques remains essential for achieving system security as well as testing system resistance levels in the cybersecurity field. Current Linux systems store password information within the /etc/shadow file using cryptography methods such as yescrypt and sha512crypt along with alternative algorithms. This blog outlines the methods to analyze password hashes with John the Ripper and Hashcat as well as alternative specialized tools for decryption.</p><h4>Understanding Linux Password Hashes</h4><p>The Linux system places user password information within the /etc/shadow file, which is accessible only to privileged users such as root. The file contains one account entry per line where each entry contains password hash data and related account details. Let’s break down an example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1013/1*M-1LugXUcNBHMRRHIGf-SQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qEiPtKeLV9pJ9VkoYbuA0g.png" /></figure><pre>kali:$y$j9T$ufXTBpN1QpgwlgqRFmb/B0$/.y0ybAF4iNQXniErsDWf9QSl2HZH7LnBeRHB4ZiQa9:20057:0:99999:7:::<br></pre><h4>Components of the Hash Entry</h4><ol><li><strong>Username:</strong> kali</li><li><strong>Password Hash:</strong> $y$j9T$ufXTBpN1QpgwlgqRFmb/B0$/.y0ybAF4iNQXniErsDWf9QSl2HZH7LnBeRHB4ZiQa9</li></ol><ul><li>This is the actual password hash.</li><li>It uses the yescrypt algorithm, as indicated by the $y$ prefix.</li><li>Structure:</li><li>$y$: Indicates the yescrypt algorithm.</li><li>j9T: Parameters for hashing (cost factors, memory usage).</li><li>ufXTBpN1QpgwlgqRFmb/B0: Salt used during hashing.</li><li>/.y0ybAF4iNQXniErsDWf9QSl2HZH7LnBeRHB4ZiQa9: The hashed password.</li></ul><h4>Metadata Fields:</h4><ul><li>20057: Last password change date (in days since January 1, 1970).</li><li>0: Minimum password age (days before the password can be changed again; 0 means no restriction).</li><li>99999: Maximum password age (days after which the password must be changed; 99999 effectively means no expiration).</li><li>7: Password warning period (days before expiration when the user is warned).</li><li>:::: Additional unused fields.</li></ul><h4>Common Hash Types in Linux</h4><p>Linux supports various hashing algorithms, depending on the system configuration. Below are some common hash types you may encounter:</p><p>MD5=$1$Older hashing algorithm. Rarely used in modern systems.</p><p>SHA-256=$5$Secure hashing algorithm, but slower thansha512crypt.</p><p>SHA-512=$6$Default hashing algorithm for many Linux distributions.</p><p>yescrypt=$y$Modern, computationally expensive algorithm designed to resist brute force.</p><h4>Tools for Cracking Password Hashes</h4><p>The security of password hashes can be checked through specialized tools including John the Ripper, and Hashcat as well as other tools available on the market. The following section explains the operation of each tool while offering specific information to break various hash types.</p><p><strong>John the Ripper: </strong>John the Ripper is a versatile password-cracking tool that supports a wide range of hash formats. Here’s how to use it:</p><ol><li>Extract the hash portion from /etc/shadow and save it in a file (e.g., passwords.txt.txt):</li><li>kali:$y$j9T$ufXTBpN1QpgwlgqRFmb/B0$/.y0ybAF4iNQXniErsDWf9QSl2HZH7LnBeRHB4ZiQa9</li><li>Run John with the appropriate format:</li></ol><ul><li>For yescrypt:<br>john — format=crypt — wordlist=/usr/share/wordlists/rockyou.txt passwords.txt</li><li>For sha512crypt ($6$):<br>john — format=sha512crypt — wordlist=/usr/share/wordlists/rockyou.txt passwords.txt</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v8wNdDOFl9qt6JIqVuz-Ag.png" /><figcaption>View the cracked password: john — show hash.txt</figcaption></figure><h4>Tips:</h4><ul><li>John automatically detects the hash type when using --format=crypt.</li><li>It supports dictionary attacks (--wordlist) and brute-force attacks (--incremental).</li></ul><p><strong>Hashcat: </strong>Hashcat is a GPU-accelerated password-cracking tool that excels at high-speed cracking. It supports a wide range of hash modes and is highly configurable. Steps to Crack a Hash:</p><ol><li>Identify the hash mode:</li></ol><ul><li>yescrypt: Mode -m 28800</li><li>sha512crypt: Mode -m 1800</li></ul><ol><li>Run Hashcat with the appropriate mode:</li></ol><ul><li>For yescrypt: <br>hashcat -m 28800 -a 0 passwords.txt /usr/share/wordlists/rockyou.txt</li><li>For sha512crypt: <br>hashcat -m 1800 -a 0 passwords.txt /usr/share/wordlists/rockyou.txt</li></ul><h4>Tips:</h4><ul><li>Hashcat leverages GPU power for faster cracking.</li><li>Use the -a flag to specify the attack mode:</li><li>0: Dictionary attack.</li><li>3: Brute-force attack.</li><li>6: Hybrid attack (dictionary + rules).</li></ul><p><strong>Hydra: </strong>Hydra is primarily used for online brute-forcing (e.g., SSH, FTP) but can also be used to test password strength against services.<br>Example: hydra -l kali -P /usr/share/wordlists/rockyou.txt ssh://192.168.1.10</p><p><strong>CrackStation: </strong>For simple hashes (e.g., MD5, SHA-1), you can use online tools like <a href="https://crackstation.net/">CrackStation </a>to check if the hash has been precomputed.</p><h4>Techniques for Hash Cracking</h4><p>1. <strong>Rule-Based Attacks: </strong>Both John and Hashcat support rule-based attacks, which transform words from dictionaries through operations like number insertion and letter capitalization.<br>Example: john — rules — wordlist=/usr/share/wordlists/rockyou.txt hash.txt</p><p>2. <strong>Mask Attacks: </strong>Using Hashcat enables the implementation of mask attacks which allow users to define specific patterns as password constraints (such as ?u?l?l?l?d?d for a combination of uppercase and lowercase and digits).<br>Example: hashcat -m 1800 -a 3 passwords.txt ?u?l?l?l?d?d</p><p>3.<strong> Rainbow Tables: </strong>The precalculation of hashes with common passwords constitutes Rainbow tables. Salted hashes reduce the effectiveness but dictionaries remain effective against unsalted hash types.</p><h4>Conclusion</h4><p>Ethical hackers and system administrators need to master Linux password hash cracking because this ability proves essential for their work. John the Ripper and Hashcat together with other tools allow users to measure system security by uncovering weak passwords. The yescrypt algorithm delivers strong protection but attackers with sufficient resources can still overcome its defenses.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12dfb9e1dc2f" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/cracking-linux-password-hashes-12dfb9e1dc2f">Cracking Linux Password Hashes</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mapping the Application]]></title>
            <link>https://medium.com/@NiaziSec/mapping-the-application-a922729a6772?source=rss-171b87d2579------2</link>
            <guid isPermaLink="false">https://medium.com/p/a922729a6772</guid>
            <category><![CDATA[web-mapping]]></category>
            <category><![CDATA[bug-bounty-hunter]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[bug-bounty-program]]></category>
            <dc:creator><![CDATA[Muhammad Abdullah Niazi]]></dc:creator>
            <pubDate>Sun, 23 Feb 2025 06:52:49 GMT</pubDate>
            <atom:updated>2025-02-23T06:52:49.620Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Web Application Hacker’s Handbook</h4><p>The ultimate objective is to build a complete comprehension of how the application operates by understanding its functionality and behavioral patterns while locating its security protection areas. Full comprehension enables you to detect vulnerabilities precisely. This blog will only cover how to map the web application before testing which is a crucial step.</p><ul><li><strong>Enumerate Content and Functionality: </strong>Create a map that demonstrates all the features together with the content elements available in the application.</li><li><strong>Examine Behavior and Security Mechanisms: </strong>Analyze how the application processes inputs, maintains sessions, enforces authentication, and implements data validation. Look at both the client-side (e.g., JavaScript) and server-side (e.g., database interactions, API endpoints) components.</li><li><strong>Identify the Attack Surface: </strong>Determine all points through which attackers can connect with the application during the attack surface identification process. The extent of your mapping investigation determines how many vulnerabilities you will identify during analysis.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/921/0*imFig4nsTOaIqltG.png" /><figcaption><a href="https://www.schellman.com/blog/cybersecurity/using-mind-maps-application-security-testing">https://www.schellman.com/blog/cybersecurity/using-mind-maps-application-security-testing</a></figcaption></figure><h4>2. Content Enumeration Techniques</h4><p>A complete listing of accessible application contents requires identification of all pages and forms in addition to listing all capabilities.</p><ul><li><strong>Manual Browsing: </strong>The assessment starts with manual browsing which means following each link beginning from the homepage.</li></ul><h4><strong>Web Spidering:</strong></h4><ul><li><strong>Automated Crawling: </strong>Systematic tools perform automated page requests that extract HTML links before they recursively follow them.</li><li><strong>Enhanced Methods: </strong>Enhanced tools provide functionalities that perform document submission through pre-defined values and random inputs to reach deeper parts of a website.</li><li><strong>JavaScript Parsing: </strong>Advanced spiders analyze client-side scripts to extract additional URLs that are dynamically generated.</li><li><strong>Popular Tools: </strong>These popular tools include Burp Suite together with WebScarab Zed Attack Proxy and CAT which automate procedures during security evaluation.</li><li><strong>robots.txt File: </strong>The robots.txt File located in the site root contains a directory whitelist that instructs web crawlers which parts of the application to avoid exploring yet reveals application areas considered sensitive or hidden to external spiders.</li></ul><h4>3. Limitations of Fully Automated Spidering</h4><p>Automated tools have restricted abilities in revealing the full application content.</p><ul><li><strong>Unusual Navigation Mechanisms: </strong>FeedBot automation struggles to understand complicated JavaScript interfaces along with dynamic areas that automated scanners cannot reach.</li><li><strong>Compiled Client-Side Objects: </strong>Flash and Java applets contain content that spiders cannot process because they need to interpret compiled code which remains undetectable.</li><li><strong>Multistage Functionality: </strong>The incorrect system input of valid context-specific data during multistage submissions might prevent automated progress because invalid entry will cause failure.</li><li><strong>URL-Based Content Identification: </strong>The identification method that uses URLs exists as a primary content-distinguishing method among spiders. These pages present problems due to their ability to provide different content for the same URL based on parameter changes. This results in missed content sections.</li><li><strong>Volatile Data in URLs: </strong>When timers or random values are included in URL parameters spiders might create endless and unique URLs that can significantly reduce the crawl rate.</li></ul><h4><strong>Authentication Issues:</strong></h4><ul><li><strong>Session Disruption: </strong>Tools running automation might create session disruptions through user session termination or submission of wrong data which results in session interruption.</li><li><strong>Per-Page Tokens: </strong>Security tokens used on a per-page basis can lose their effectiveness when pages are requested in an improper order.</li></ul><h4>4. Risks of Automated Spidering</h4><p>Show the possible hazards that occur when conducting automatic crawling procedures on operative applications.</p><ul><li><strong>Dangerous Functionality: </strong>The automated spidering process has the potential to activate dangerous system operations such as delete functions thus unintentionally causing substantial damage.</li><li><strong>Example Scenario: </strong>An automated tool might access edit or delete functions of a content management system through its unprotected interface thereby leading to momentary defacements and permanent data losses until sufficient protection mechanisms are implemented.</li></ul><h4>5. User-Directed Spidering</h4><p>Users should use automated methods alongside manual exploration to create safe application mapping procedures.</p><ul><li><strong>Manual Control: </strong>The user operates the application through their standard internet browser navigation methods. During the test period, an intercepting proxy works as a middle point between users and resources to record and track all HTTP traffic made through Burp Suite or WebScarab.</li></ul><h4><strong>Advantages:</strong></h4><ul><li><strong>Handling Complex Navigation: </strong>Human judgment can navigate through dynamic elements and non-standard interfaces better than an automated tool.</li><li><strong>Valid Data Submission: </strong>During the input phase the user verifies all data is suitable for submission to maintain proper automated mapping functionality.</li><li><strong>Session Management: </strong>The user stays logged in to handle session expiry re-authentication thus maintaining continuous mapping operations.</li><li><strong>Controlled Interaction with Dangerous Functions: </strong>The user can understand what dangerous features exist by avoiding automatic execution.</li></ul><h4>6. Proxy/Spider Tool Workflow</h4><p>Leveraging proxy tools enables users to map an application while they secure all important traffic data.</p><ul><li><strong>Traffic Monitoring: </strong>Traffic Monitoring functions as a tool that redirects and records every HTTP request along with the response during the application usage period.</li><li><strong>Site Map Building: </strong>The tool uses generated data to build visual or structured maps that display all reachable URLs and detected functionalities.</li><li><strong>Discretion in Requesting Functions: </strong>Requestable functions remain under user control through this feature since it stops the tool from unintentionally performing dangerous tasks.</li></ul><h4>7. Best Practices</h4><p>The application mapping process needs methodologies that both reach maximum coverage points and reduce potential risks.</p><ul><li><strong>Avoid Fully Automated Spidering:</strong> When operating in complex or sensitive environments users should direct their tools through manual and user-controlled means to avoid unanticipated errors.</li><li><strong>Handle Authentication Carefully: </strong>The automation systems need to execute operations with correct session tokens or proper credentials. Regular monitoring of active sessions should happen to prevent accidental logouts from occurring.</li><li><strong>Caution with Dangerous Functions: </strong>Do not activate discovered dangerous functions (such as account deletion URLs) regardless of their potential harmfulness. The review should be conducted manually for any risky functions.</li></ul><h4>8. Discovering Hidden Content</h4><p>Determine resources that exist outside the main navigation links of the application.</p><ul><li><strong>Backup Files and Archives: </strong>The analysis should include checking for backup copies of active files through alternative file extensions and archive snapshots of the application.</li><li><strong>New or Unlinked Functionality: </strong>Test features developed by developers occasionally find their way into the system without specific connection points from the main user interface.</li><li><strong>Default and Old Versions: </strong>Off-the-shelf applications often include default pages together with older file versions that can possibly contain well-known vulnerabilities.</li><li><strong>Configuration and Source Files: </strong>Configuration files along with source code documents occasionally remain accessible to the public thus exposing important secrets like database login credentials.</li><li><strong>Comments and Log Files: </strong>The developer comments added to source code files along with application log entries sometimes provide discovery opportunities for system user names technical error control features and system reactions.</li></ul><h4>9. Brute-Force Techniques</h4><p>Software applications use automated methods for guessing hidden parts of the application interface through multiple trial attempts.</p><ul><li><strong>Automated Requests:</strong><br> Tools generate numerous requests targeting common and estimated directory names to find hidden content through automated methods.</li><li><strong>Tools and Methodology: </strong>Burp Intruder serves as an example of a tool that automatically tests hidden pages by running through lists of directory names and parameter values.</li></ul><h4><strong>Interpreting Response Codes:</strong></h4><ul><li><strong>302 Found:</strong> The response 302 Found may show that your system has redirected you either to a login page or an error page.</li><li><strong>400 Bad Request:</strong> Suggest a non-standard naming scheme.</li><li><strong>401 Unauthorized/403 Forbidden:</strong> Resource existence confirms through 401 Unauthorized/403 Forbidden status that specific access requirements must be fulfilled for proper entry.</li><li><strong>500 Internal Server Error:</strong> When your computer displays the 500 Internal Server Error you can discover potential parameters which the application demands thus revealing undisclosed functionality.</li></ul><h4>10. Inference from Published Content</h4><p>The existing information within public application sections helps detect previously hidden application features.</p><ul><li><strong>Naming Schemes and Patterns: </strong>Test the naming schemes of visible application sections because they can help predict unavailable page or functionality names.</li><li><strong>Numeric Identifiers: </strong>Other similar resources will likely exist when URLs contain sequential or patterned numeric values.</li><li><strong>Client-Side Clues: </strong>HTML or JavaScript comments together with disabled form elements help reveal supplemental server-side functionalities.</li></ul><h4>11. Use of Public Information</h4><p>Electronic sources and search engine tools help discover old public content as well as resources mentioned in external links.</p><ul><li><strong>Search Engines: </strong>Use targeted queries with operators like site:, link:, and related: to locate pages that might not be directly linked to the current site.</li><li><strong>Web Archives: </strong>The Wayback Machine but also other web archives display previous iterations of website pages to show both content that disappeared from current versions and material hidden from view.</li></ul><h4>12. Leveraging the Web Server</h4><p>Access additional information by taking advantage of possible weaknesses in the web server application itself or its foundation settings.</p><ul><li><strong>Banner Grabbing: </strong>The analysis of HTTP server headers through banner grabbing allows researchers to detect different server details including operational version and platform information that could reveal possible weaknesses.</li><li><strong>Default Content and Diagnostic Scripts: </strong>Multiple websites use default built-in content pages and diagnostic scripts from their web servers that remain accessible through potential security holes.</li><li><strong>Third-Party Components: </strong>Third-Party Components like standardized shopping carts and forums rack known security challenges unless they receive required updates or proper configuration.</li></ul><h4>13. Identifying Entry Points for User Input</h4><p>User-supplied data entry points should be documented for every section where applications accept this data because such points represent primary attack routes.</p><ul><li><strong>URL Strings and Query Parameters: </strong>A full examination must be applied to every part of the URL leading to the query marker and all offered parameters.</li><li><strong>POST Data: </strong>The probability of attack exists through unvalidated POST body data forms that users submit to the application.</li><li><strong>Cookies and HTTP Headers: </strong>User-Agent and Referer headers along with cookies can be manipulated to create extra entry points into the system.</li></ul><h4>14. Analyzing the Application</h4><p>Dive into the main application tasks in addition to subsidiary elements whose purpose is to find security weaknesses.</p><ul><li><strong>Core Functionality: </strong>Core Functionality should be studied both in terms of application purposes and normal request processing mechanisms.</li><li><strong>Peripheral Behavior: </strong>The examination must include study of off-site connections together with error handling elements and administrative controls as well as logging components and redirect mechanics.</li><li><strong>Security Mechanisms: </strong>Study how session maintenance along with access restriction protocols verification methods and security defense systems implement protocols.</li><li><strong>Technology Stack: </strong>Application researchers need to detect all utilized client-side components (checks forms, scripts, and rich client components) in addition to server-side elements (including dynamic pages, SSL encryption, databases, and email systems) in the technology stack.</li></ul><h4>15. Identifying Server-Side Technologies</h4><p>The organization should identify all server technologies because this discovery will reveal existing security weaknesses and configuration problems.</p><ul><li><strong>Banner Grabbing: </strong>The HTTP Server header analysis enables you to gather server software information through Banner Grabbing.</li><li><strong>File Extensions: </strong>Extensions such as .asp, .jsp, or .php reveal the platform or language the application is built with.</li><li><strong>Session Tokens: </strong>The naming conventions for session tokens (e.g., JSESSIONID for Java-based systems or PHPSESSID for PHP) provide clues about the underlying technology.</li><li><strong>Third-Party Components: </strong>The analysis should include the identification of all open-source and commercial libraries that make up the application since they could have documented vulnerabilities.</li></ul><h4>16. Mapping the Attack Surface</h4><p>List all possible weak points where attackers could perform their attacks.</p><ul><li><strong>Client-Side Validation vs. Server-Side Checks: </strong>Application security relies on identical validation protocols executed at both the client and server levels yet sometimes these protocols remain unconnected between these platforms.</li><li><strong>Database Interaction: </strong>The application faces injection attack risks at locations where it executes SQL queries.</li><li><strong>File Handling: </strong>The file handling features including upload/download activity have potential vulnerabilities because attackers can perform path traversal attacks and inject harmful scripts.</li><li><strong>User-Supplied Data Display: </strong>What follows is the weak handling of user-supplied data during display operations that results in cross-site scripting (XSS) vulnerabilities.</li><li><strong>Dynamic Redirects and Header Injection: </strong>Attacker control over dynamic redirects and header injection occurs when redirection logic is poorly managed by web application software and websites.</li><li><strong>Social Features and Login Mechanisms: </strong>The integration of social features and login methods through comment sections and login forms creates possible threats from brute-force attacks merged with enumeration vulnerabilities.</li><li><strong>Session and Access Controls: </strong>Predictable session tokens or flawed privilege checks can facilitate unauthorized access.</li><li><strong>Error Handling: </strong>The backend reveals critical information when the system produces thorough error messages.</li><li><strong>Email and External Interfaces: </strong>Email systems and external interface APIs have the risk of getting infected through injection vulnerabilities.</li><li><strong>Native Code Components</strong> exhibit weaknesses caused by memory corruption vulnerabilities which can lead to buffer overflows.</li><li><strong>Third-Party Application Components:</strong> Third-Party Application Components comprise standardized components such as forums and shopping carts which can be exploited when developers fail to install current security updates.</li><li><strong>Web Server Software: </strong>The combination of incorrect server software configurations together with outdated software creates established weak points.</li><li><strong>/core Path: </strong>The site stats page functions as an example of vulnerable code structure by receiving multiple parameters divided by the delimiter (e.g., |). This might be susceptible to brute force attempts where parameters such as source, location, or IP can be manipulated.</li></ul><h4>Summary</h4><p>Using manual and automated tools creates a well-rounded approach to mapping out both application structure and security weaknesses in a protected manner.</p><ul><li><strong>Core Methodology: </strong>Begin by performing manual assessments to gain knowledge about crucial operational aspects. Automated supplementations should replace repetitive tasks but need strict session and validation monitoring. Brute force and inference methods should be used to detect hidden resources. Please analyze every component of the application starting from core functions up to peripheral activities by focusing on security mechanisms.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a922729a6772" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Application Technologies]]></title>
            <link>https://medium.com/@NiaziSec/web-application-technologies-aaa947303675?source=rss-171b87d2579------2</link>
            <guid isPermaLink="false">https://medium.com/p/aaa947303675</guid>
            <category><![CDATA[web-technology]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[bug-bounty-program]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-hunter]]></category>
            <dc:creator><![CDATA[Muhammad Abdullah Niazi]]></dc:creator>
            <pubDate>Sat, 22 Feb 2025 13:27:50 GMT</pubDate>
            <atom:updated>2025-02-22T13:30:54.961Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Web Application Hacker’s Handbook</h4><p>Web applications constitute an extensive domain that keeps developing in real time. The HTTP protocol serves as a base while Ajax and HTML5 represent modern frameworks that developers and security professionals must grasp completely. In this blog, we’ll cover how web applications work as well as their operational capabilities together with security concerns they generate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DhE7mUXn0ts5GN8W.png" /></figure><h4>1. The HTTP Protocol: The Backbone of the Web</h4><p>HTTP stands as a request-response protocol that makes servers communicate with clients through a stateless framework across the web. The communication basis of this protocol is TCP which operates through port 80 for HTTP and port 443 for HTTPS under the following structure.</p><h4><strong>HTTP Methods &amp; Associated Vulnerabilities:</strong></h4><ul><li>Caching or bookmarking of parameters through GET methods exposes users to sensitive information because both logging and caching of such data can happen without proper security handling.</li><li>POST allows transmitting request body data which protects URL data exposure but fails to shield against CSRF assaults.</li><li>HEAD operates similarly to GET while eliminating the response body for reconnaissance purposes.</li><li>The TRACE method provides an opportunity for attackers to conduct XSS attacks which enable cookie theft even when web servers implement the HttpOnly flag.</li><li>The HTTP OPTIONS method reveals the collection of permissible methods which sometimes exposes additional or improperly configured endpoints.</li></ul><h4>Common headers include:</h4><ul><li>Content-Type: Specifies the MIME type of the content (e.g., application/json, text/html).</li><li>Cookie: Carries session identifiers or other user-specific data.</li><li>Authorization: Used for authentication (e.g., Basic Auth, Bearer tokens).</li><li>Cache-Control: Controls caching behavior.</li></ul><h4>Misconfigured headers can lead to vulnerabilities such as:</h4><ul><li>Missing Strict-Transport-Security (HSTS), allowing downgrade attacks.</li><li>Insecure Content-Security-Policy (CSP), enabling XSS.</li><li>Improper use of Access-Control-Allow-Origin, leading to Cross-Origin Resource Sharing (CORS) misconfigurations.</li></ul><h4><strong>Common Header-Based Vulnerabilities:</strong></h4><ul><li>The vulnerability allows attackers to exploit incorrect validation in multi-tenant applications which results in SSRF as well as password reset attacks.</li><li>Sensitivity data theft occurs through malicious websites when CORS configurations allow the wildcard (*) character or any origin in the Access-Control-Allow-Origin header.</li><li>Non-compliant content-type validation creates opportunities for MIME-type confusion attacks to occur. The unexpected functionality created by multiple parameters sharing identical names within one request makes up HTTP Parameter Pollution (HPP).</li><li>HTTP Verb Tampering takes advantage of server misconfigurations through the use of uncommon verbs like TRACE and DELETE. The combination of insecure redirects along with forwards enables attackers to route victims toward damaging sites.</li></ul><h4><strong>Client-Side Technologies</strong></h4><p>Modern web applications use JavaScript, HTML, and CSS to create interactive user experiences, but improper implementation introduces security risks:</p><ul><li><strong>DOM-Based Cross-Site Scripting (XSS): </strong>Unsafe input executed through the DOM modification by JavaScript can cause XSS vulnerabilities when certain commands run like document.write(location.hash);When dealing with these vulnerabilities it is best practice to employ two strategies: Use innerText instead of innerHTML, implement a Content Security Policy (CSP), and sanitize inputs.</li><li><strong>Client-Side Storage Risks: </strong>Data inside LocalStorage and SessionStorage remains accessible through JavaScript yet it has vulnerabilities to cross-site scripting (XSS) attacks. The data stored in IndexedWebSQL remains at risk when security measures are implemented incorrectly. The storage of sensitive data should occur server-side in addition to the implementation of CSP to prevent script execution.</li><li><strong>Ajax and JSON Vulnerabilities: </strong>The exposure of sensitive JSON data through GET requests will allow hackers to steal data with malicious JavaScript embedded in a &lt;script&gt; tag. To mitigate such attacks use proper CORS headers and X-Requested-With checks.</li></ul><h4>3. Server-Side Technologies: The Engine Behind the Scenes</h4><p>Business logic with databases and dynamic content processing belongs to backend technologies which deliver multiple security risks. Some popular frameworks are,</p><ul><li>Internet developers heavily rely on PHP to develop websites for WordPress along with Joomla which uses this framework extensively.</li><li>The enterprise application development framework ASP.NET belongs to Microsoft.</li><li>Java EE: Supports large-scale systems with features like EJB and JPA.</li><li>Through Node.js applications scale up using its asynchronous JavaScript runtime solution.</li></ul><h4>Database Interaction:</h4><ul><li>Both MySQL and PostgreSQL databases act as examples of SQL database systems designed for storing structured data types.</li><li>NoSQL databases including MongoDB and Redis manage datasets that lack a fixed structure or have an intermediate configuration.</li></ul><p><strong>Authentication and Authorization: </strong>Access control systems are managed through the authentication tools OAuth and JWT together with SAML. Session management ensures user identity persistence across requests.</p><h4>Potential Vulnerabilities :</h4><ul><li>SQL Injection attacks occur through database query manipulation by processing unvalidated input data. Example: “ OR 1=1 — in a login form.</li><li>Remote Code Execution (RCE) originates from insecure deserialization methods or unverified code execution.</li><li>Server-side request Forgery attacks enable unauthorized parties to execute requests against the server&#39;s system.</li><li>Local File Inclusion (LFI) along with Remote File Inclusion (RFI) offer attackers two methods to disclose internal files or execute arbitrary code.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*p-KGG8jp8gH8MWr5wZ_MHg.png" /><figcaption><a href="https://www.geeksforgeeks.org/web-technology/">https://www.geeksforgeeks.org/web-technology/</a></figcaption></figure><p><strong>Mitigation:</strong> Web application firewalls (WAFs) and prepared statements and parameterized queries should be utilized for mitigation purposes. The protection plan should include MFA and rate-limiting along with secure session cookies that use the Secure HttpOnly and SameSite attributes.</p><h4>4. Encoding Schemes: Ensuring Safe Data Transmission</h4><p>Attackers take advantage of encoding that secures data transmission although this method remains vital for security purposes.</p><ul><li>URL Encoding: Replaces reserved characters (e.g., &amp;, =) with percent-encoded equivalents (e.g., %26, %3D). Prevents syntax errors in URLs.</li><li>Unicode and UTF-8: Support global character sets, ensuring compatibility across languages.</li><li>HTML Encoding: Escapes special characters (&lt;, &gt;, &amp;) to prevent script execution. Example: &lt;script&gt; becomes &amp;lt;script&amp;gt;.</li><li>Base64 Encoding: Converts binary data into ASCII-compatible strings for safe transmission.</li></ul><p><strong>Potential Vulnerabilities: </strong>The filtering system can be bypassed through multiple encodings of payload content. Bad decoding procedures create injection vulnerabilities when programmers handle input incorrectly. Errors during data normalization can lead to file system breaches through directory traversals and command execution intents.</p><p><strong>Mitigation:</strong> The use of OWASP Java Encoder together with HTMLPurifier for PHP can function as standard input validation libraries to achieve mitigation.</p><h4>5. State Management: Tracking User Interactions</h4><p>Applications implement cookies and sessions as well as tokens to maintain user state since HTTP lacks built-in state preservation capabilities. The server receives small text files named cookies during each client-side request through which they store data on the client machine. Attackers can obtain unauthorized access through stolen cookies which also lets them collect session tokens when an XSS vulnerability exists. Some cookie attributes are,</p><ul><li>Secure: An additional attribute to secure offers protection by enabling HTTPS transmission of cookies.</li><li>HttpOnly: Prevents JavaScript access.</li><li>SameSite: The SameSite attribute protects against CSRF by stopping unauthorized cross-domain request Transmission.</li></ul><p><strong>Session: </strong>A session enables the server to store user-specific data through session IDs that are stored on the server side. The system uses cookies or tokens as implementation methods for this technique. The major weakness of sessions involves attackers imposing a specific session ID onto their victims making them use it.</p><p><strong>JWT (JSON Web Token) Issues: </strong>Although JWT (JSON Web Token) presents none of its own vulnerabilities the Algorithm Attack becomes possible when “alg=none” is accepted by servers.</p><p><strong>Mitigation:</strong> Set Secure, HttpOnly, and SameSite=Strict attributes to prevent theft and CSRF. Regenerate session IDs upon authentication. Enforce strong cryptographic signing and expiration checks.</p><h4>Conclusion</h4><p>Rich interactive web application technologies have vastly evolved while creating new security threats for their systems. You can produce safe and efficient applications by studying HTTP and client-side scripting along with server-side processing and encoding schemes and state management fundamentals. It is essential for security professionals and developers to stay updated about these emerging technologies because they need to understand the modern developments in web technology.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aaa947303675" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Core Defense Mechanisms]]></title>
            <link>https://medium.com/@NiaziSec/core-defense-mechanisms-b9ac54c29e52?source=rss-171b87d2579------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9ac54c29e52</guid>
            <category><![CDATA[defense-mechanism]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Muhammad Abdullah Niazi]]></dc:creator>
            <pubDate>Thu, 20 Feb 2025 12:14:29 GMT</pubDate>
            <atom:updated>2025-02-20T12:14:29.588Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Web Application Hacker’s Handbook</h4><p>Web applications experience continuous security dangers, they need multilevel security systems. Attackers take advantage of authentication weaknesses, input validation flaws, and session management issues to penetrate security systems. The blog examines fundamental security systems alongside their technical systems together with best practices to protect against web application attacks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/924/1*TfM93R5HvZlZ16Y5wnVCqA.png" /></figure><h4>Four Pillars of Web Application Security</h4><ol><li>User Access Control operates as a security measure which enforces authentication together with authorization for access restrictions.</li><li>All user input needs validation combined with proper sanitization to defend against injection attacks.</li><li>Attack Handling requires organizations to execute countermeasures for fighting direct security attacks.</li><li>Security monitoring together with logging and administrative oversight functions should be enabled through Application Management.</li></ol><h4>1. User Access Control Mechanisms</h4><ul><li>Basic Authentication: Username/password verification.</li><li>Multi-Factor Authentication (MFA): Combines multiple verification factors (password + OTP).</li><li>Token-Based Authentication: JWT, OAuth, or API keys for secure session handling.</li><li>Biometric Authentication: Uses fingerprints, facial recognition, or retina scans.</li></ul><h4>Technical Implementation: Secure Authentication Handling</h4><ul><li><strong>Hash passwords using strong algorithms</strong>:</li></ul><pre>import bcrypt  <br>password = b&quot;supersecret&quot;  <br>hashed = bcrypt.hashpw(password, bcrypt.gensalt())</pre><ul><li><strong>Use secure session management</strong> (HTTP-only and Secure cookies):</li></ul><pre>from flask import Flask, session  <br>app = Flask(__name__)  <br>app.config[&#39;SESSION_COOKIE_HTTPONLY&#39;] = True  <br>app.config[&#39;SESSION_COOKIE_SECURE&#39;] = True</pre><ul><li><strong>Implement MFA (e.g., TOTP-based 2FA using PyOTP):</strong></li></ul><pre>import pyotp  <br>totp = pyotp.TOTP(&quot;JBSWY3DPEHPK3PXP&quot;)  <br>print(totp.now())</pre><h4>2. Secure Session Management</h4><ul><li>The JWT (JSON Web Tokens) represents a self-contained authentication token that includes both cryptographic verification and authentication capabilities.</li><li>Hidden Form Fields function within older programs but still remain prone to malicious changes from attackers.</li></ul><h4>Technical Implementation: Secure Session Handling</h4><ul><li><strong>Use Secure &amp; HTTP-only flags for cookies:</strong></li></ul><pre>Set-Cookie: sessionid=abc123; HttpOnly; Secure; SameSite=Strict</pre><ul><li><strong>Rotate session IDs after authentication:</strong></li></ul><pre>session[&#39;user_id&#39;] = new_session_id</pre><ul><li><strong>Expire sessions after inactivity:</strong></li></ul><pre>app.config[&#39;PERMANENT_SESSION_LIFETIME&#39;] = timedelta(minutes=30)</pre><h4>3. Input Handling: Preventing Injection Attacks</h4><p>The three available methods encompass whitelist filtering for approved input and blacklist filtering for blocking unsafe content and sanitization methods through character encoding or removal while parameterized queries stop SQL injection and semantic validation checks for logical input validity.</p><h4>Technical Implementation: Secure Input Handling</h4><ul><li><strong>Use Parameterized Queries (SQL Injection Prevention):</strong></li></ul><pre>cursor.execute(&quot;SELECT * FROM users WHERE username = ?&quot;, (user_input,))</pre><ul><li><strong>Sanitize Input for XSS Prevention:</strong></li></ul><pre>from markupsafe import escape  <br>safe_input = escape(user_input)</pre><ul><li><strong>Apply Allow-List Input Validation:</strong></li></ul><pre>import re  <br>if not re.match(&quot;^[a-zA-Z0-9_]+$&quot;, user_input):  <br>    raise ValueError(&quot;Invalid input!&quot;)</pre><h4>4. Handling Web Attacks with Security Monitoring</h4><ul><li>Rate Lifting Together with Throttling acts as a shield against brute-force attacks.</li><li>WAF (Web Application Firewall) — Blocks common attack patterns.</li><li>Logging &amp; Monitoring — Tracks suspicious activities.</li><li>The error handling procedure works to conceal system information from attackers.</li></ul><h4>Technical Implementation: Security Controls</h4><ul><li><strong>Rate limiting using Flask-Limiter:</strong></li></ul><pre>from flask_limiter import Limiter  <br>limiter = Limiter(app, key_func=get_remote_address)  <br>@app.route(&quot;/login&quot;)  <br>@limiter.limit(&quot;5 per minute&quot;)</pre><ul><li><strong>Enable logging for security events:</strong></li></ul><pre>import logging  <br>logging.basicConfig(filename=&quot;security.log&quot;, level=logging.WARNING)  <br>logging.warning(&quot;Suspicious login attempt detected&quot;)</pre><ul><li><strong>Configure Content Security Policy (CSP) for XSS Prevention:</strong></li></ul><pre>Content-Security-Policy: default-src &#39;self&#39;; script-src &#39;self&#39;</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9ac54c29e52" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Web Application Hacker’s Handbook: Web Application (In)security]]></title>
            <link>https://medium.com/@NiaziSec/the-web-application-hackers-handbook-web-application-in-security-b2e7df531100?source=rss-171b87d2579------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2e7df531100</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[web-application-security]]></category>
            <dc:creator><![CDATA[Muhammad Abdullah Niazi]]></dc:creator>
            <pubDate>Wed, 19 Feb 2025 17:47:51 GMT</pubDate>
            <atom:updated>2025-02-19T17:47:51.356Z</atom:updated>
            <content:encoded><![CDATA[<h4>Discovering and Exploiting Security Flaws</h4><p>The security needs of early websites consisted only of protecting web servers since these structures provided stationary information channels. The main security concerns at this time were targeted at website defacement along with resource misuse incidents.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/0*BUpQHAIDDqIkAYzB.png" /><figcaption><a href="https://www.imperva.com/learn/application-security/web-application-security/">https://www.imperva.com/learn/application-security/web-application-security/</a></figcaption></figure><p>Current web applications provide interactive two-way operations for security-demanding transactions including financial operations and authentication systems. Data security remains essential because system flaws result in customer information breaches combined with fraudulent activity and malicious assaults against end-users. Software programs routinely get developed by programmers who lack robust security skills leading to additional operational vulnerabilities.</p><h4>Common Web Application Functions</h4><p>Basic web applications drive key online platforms including shopping through Amazon and social networking via Facebook as well as social and financial services at Citibank together with search technology at Google. Enterprise organizations utilize web applications for both human resource management and business administration purposes and HR operations. Web interfaces replacing legacy application systems such as ERP and email clients have made web browsers the fundamental software used by users.</p><h4>Why Web Applications Dominate</h4><ul><li>HTTP delivers reliable and effective security due to its ability to work through proxy and tunnel services.</li><li>Web applications deliver seamless access because they do not require any software installation for clients and automatic instant update functionality.</li><li>The user interface in browsers creates advanced graphical interfaces that allow people-friendly interactions.</li><li>Developers can access quick development capability through open-source resources using simple technologies.</li></ul><h4>Web Application Security Challenges</h4><p>Web applications create distinct system vulnerabilities because new technologies and attack approaches constantly emerge. Major threats include:</p><ul><li>Broken Authentication (67%)</li><li>Broken Access Controls (78%)</li><li>SQL Injection (36%)</li><li>Cross-Site Scripting (91%)</li><li>Information Leakage (81%)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*FyYDZKTP3LW4EXX8.jpg" /><figcaption><a href="https://www.etatvasoft.com/insights/what-is-web-application-security/">https://www.etatvasoft.com/insights/what-is-web-application-security/</a></figcaption></figure><h4>Misconceptions About Security</h4><p>Online websites promote SSL encryption to reassure customers yet SSL encryption serves just to protect data while it moves between systems. The implementation of SSL encryption offers no protection against Application-level vulnerabilities such as SQL injection and cross-site scripting as well as access control problems. Web platforms commonly utilize proprietary security instead of SSL and users should remain cautious about confirmation of its strength.</p><h4>The Core Security Issue: Arbitrary User Input</h4><p>An uncontrolled web client interface provides users the ability to change any transmitted data which includes request parameters cookies and headers. Security measures need to treat all incoming data as potentially dangerous so they can enforce strong validation procedures and protective measures.</p><p>Web applications remain exposed to attacks because developers fail to understand how users will interact with their programs. By utilizing specialized tools attackers can deliver unexpected input that circumvents the browser&#39;s normal functioning. Common exploits include:</p><ul><li>Attackers make price modifications by modifying hidden form fields.</li><li>The tampering of session tokens lets attackers take control of user accounts.</li><li>Attacks succeed when a user actively removes required variables in the system to activate undocumented program faults.</li><li>Injecting malicious database queries.</li></ul><p>These attacks cannot be prevented with SSL encryption since the protocol protects data transmission instead of underlying application logic.</p><h4>Key Security Problems</h4><ol><li>Web security remains an unclear concept for developers because they demonstrate less understanding of it when compared to traditional network security.</li><li>Development projects that use custom-developed applications produce specific security flaws. Web development tools help developers build applications quickly but this speed does not translate to secure applications.</li><li>Various security threats continue to develop at a faster pace than security response capabilities do. The reduction in security measures becomes necessary because limited resources force developers to focus on shorter development times or reduced budgets.</li></ol><h4>The Shift in Security Perimeter</h4><p>The traditional perimeter-based security model became obsolete because web applications now represent the main target surface. Core system security becomes exposed when attackers take advantage of application vulnerabilities by bypassing network-based defenses. Attackers use applications as entry points to reach users by taking advantage of the trusted status network-based positions these users maintain.</p><h4>Future Trends</h4><ul><li>The number of server-side vulnerabilities decreases while technological developments produce more sophisticated methods.</li><li>Attackers now direct their efforts toward system users instead of limiting themselves to application servers.</li><li>The general public shows a growing understanding of security despite the fact web applications continue to serve as a significant attack path.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2e7df531100" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Subdomain Enumeration: Expanding the Attack Surface]]></title>
            <link>https://medium.com/@NiaziSec/subdomain-enumeration-expanding-the-attack-surface-5fefe74f1d83?source=rss-171b87d2579------2</link>
            <guid isPermaLink="false">https://medium.com/p/5fefe74f1d83</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-hunter]]></category>
            <category><![CDATA[bug-bounty-program]]></category>
            <category><![CDATA[subdomains-enumeration]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <dc:creator><![CDATA[Muhammad Abdullah Niazi]]></dc:creator>
            <pubDate>Wed, 19 Feb 2025 17:36:44 GMT</pubDate>
            <atom:updated>2025-02-20T12:11:58.359Z</atom:updated>
            <content:encoded><![CDATA[<h4>Techniques and Tools</h4><p>The identification of subdomains represents a vital procedure for penetration testing. Identifying all subdomains in testing a website or an entire domain at ‘*domain.com’ leads to extending the attack opportunity. Multiple techniques exist that discover subdomains while these methods fall under two main groups: passive and active forms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lo6FPbXySdnkswxa.png" /><figcaption><a href="https://www.vaadata.com/blog/subdomain-enumeration-techniques-and-tools/">https://www.vaadata.com/blog/subdomain-enumeration-techniques-and-tools/</a></figcaption></figure><h4>Passive Techniques</h4><p>The gathering technique of passive subdomain enumeration performs information discovery by avoiding any direct interaction with the target thus making the discovery process less detectable.</p><h4>Methods of Passive Enumeration</h4><ol><li><strong>Certificate Transparency (CT): </strong>Every Certificate Authority involved in SSL/TLS certificate management must add these certificates to public Certificate Transparency logs that frequently include subdomain information. Tools: crt.sh, censys.io, Facebook&#39;s CT monitor, and Google&#39;s CT monitor.</li><li><strong>ASN Discovery: </strong>This technique discovers IP ranges available to an organization to detect its complete subdomain list.</li><li><strong>Search Engine Dorking (Google &amp; Bing): </strong>The search technique of using advanced search operators in Google &amp; Bing involves three distinct functions: site:*.example.com -www site:example.com.</li><li><strong>DNS Aggregators &amp; Public Datasets: </strong>Previously discovered subdomains are stored in public datasets found on DNS Aggregators and GitHub and VirusTotal and DNSdumpster databases.</li><li><strong>Subject Alternate Name (SAN): </strong>The analysis of SSL certificates through SAN enables the identification of supplemental domain names.</li><li><strong>Cloudflare DNS Enumeration: </strong>Leveraging Cloudflare-protected records for indirect subdomain discovery.</li></ol><h4>Active Techniques</h4><p>Direct interaction with target systems through active enumeration generates detailed results but such activity will typically produce security alerts.</p><h4>Methods of Active Enumeration</h4><ol><li><strong>HTTP Virtual Host Fuzzing: </strong>The examination of HTTP virtual hosts enables the detection of subdomains by exploring internal server configuration.</li><li><strong>HTTP Headers Analysis: </strong>Examining Host headers for internal subdomains.</li><li><strong>DNS Zone Transfers (AXFR): </strong>AXFR requests that are not properly configured will disclose the entire domain record collection.</li><li><strong>DNS Bruteforcing: </strong>The procedure of DNS Bruteforcing permits wordlists to reveal hidden subdomains.</li><li><strong>DNS Zone Walking: </strong>Zone walking using NSEC and NSEC3 records allows attackers to identify new subdomains within a domain.</li><li><strong>DNS Cache Snooping: </strong>A DNS resolver query enables snooping to reveal subdomain information from its stored cache responses.</li><li><strong>Reverse DNS Sweeping: </strong>Reverse DNS Sweeping enables researchers to return IP addresses to possible subdomains within a domain.</li><li><strong>Analyzing DNS Records (CNAME, SPF, etc.): </strong>The examination of DNS records including CNAME and SPF types yields knowledge about related domains.</li></ol><h3>Technique for Subdomain Enumeration</h3><p>Multiple software solutions exist to perform automatic subdomain enumeration operations.</p><h4>1. Automated Subdomain Enumeration Tools</h4><p>The tools exist as independent programs that only perform subdomain discovery functions.</p><ul><li><strong>Amass: </strong>The OWASP-developed Amass constitutes a strong tool featuring combined active and passive subdomain scouting abilities. This tool performs Passive DNS data gathering from Certificates Transparency Logs as well as WHOIS and its Active mode conducts brute-force attacks using wordlists. Visualization capabilities.</li><li><strong>Subfinder: </strong>Developed by ProjectDiscovery, it is an efficient tool for discovering valid subdomains. Features: Passive enumeration from various online sources. Fast and lightweight. Supports custom wordlists and rate limiting.</li><li><strong>AssetFinder: O</strong>perates as an easy-to-use tool that locates subdomains through passive methods. Focuses on speed and simplicity.</li><li><strong>Findomain: </strong>The Rust-based Findomain tool operates as a fast subdomain discovery system. Features: Parallel processing for speed. Integration with Certificate Transparency Logs. Cross-platform support.</li><li><strong>Knockpy: </strong>Through its Python language implementation Knockpy functions as a strong tool to generate subdomain lists. Combines passive and active techniques. Additional features included in this tool consist of IP resolution coupled with reverse DNS lookup capabilities.</li><li><strong>Sublist3r: S</strong>tands as one of the most popular open-source tools that achieves subdomain enumeration tasks. The tool relies on search engines as well as certificate databases and additional public source data for its operations. Can be extended with plugins.</li><li><strong>Shosubgo: </strong>A Go-based tool for subdomain enumeration. Focuses on speed and accuracy.</li><li><strong>OneForAll: R</strong>epresents an all-inclusive Python-based framework that performs subdomain enumeration. The tool implements passive discovery brute-force attacks and passive searching features.</li></ul><h4>2. Brute-Force Subdomain Enumeration Tools</h4><p>The tools run brute-force attacks against subdomains by utilizing wordlists.</p><ul><li><strong>FFuf: </strong>The fast web fuzzer FFuf serves as a tool for brief domain checks and works simultaneously with subdomain investigations. Supports parallelism and custom payloads.</li><li><strong>Dirsearch: </strong>The main purpose of Dirsearch is to function as a directory scanning system however its developers enabled subdomain enumeration functionality as an additional feature.</li><li><strong>Nmap Scripting Engine (NSE): </strong>perform subdomain brute-force attacks using dns-brute script. Command: nmap --script dns-brute --script-args dns-brute.domain=example.com,dns-brute.threads=10,dns-brute.hostlist=subdomains.txt</li></ul><h4>3. Online Services and APIs</h4><p>The service enables users to retrieve subdomain data through their APIs as well as web interfaces.</p><ul><li><strong>Censys</strong> operates as a search platform that reveals Internet-accessible devices and services to its users. Users can acquire subdomain information through the API system of this provider.</li><li><strong>Shodan:</strong> A search engine for Internet-connected devices. The system enables users to discover subdomains that belong to a particular domain.</li><li><strong>SecurityTrails:</strong> Offers a comprehensive database of domain and subdomain information. The services offer their subdomain information through free along with paid API options.</li><li>The malware analysis platform <strong>VirusTotal</strong> also functions as a subdomain information provider.</li><li>The website <strong>crt.sh</strong> operates free of charge by indexing SSL/TLS certificates. Useful for finding subdomains from Certificate Transparency Logs.</li><li><strong>PassiveTotal (Now RiskIQ): </strong>A threat intelligence platform with extensive subdomain data. Website: <a href="https://riskiq.com/">https://riskiq.com</a></li></ul><h4>4. Browser Extensions</h4><p>Unified Extensions serve as time-saving tools to obtain subdomain information.</p><ul><li><strong>SubOver: O</strong>perates as a Chrome extension that locates subdomains through passive techniques and is available at <a href="https://chrome.google.com/webstore/detail/subover.">https://chrome.google.com/webstore/detail/subover.</a></li><li><strong>sublist3r (Browser Version): </strong>A browser-based version of Sublist3r for quick subdomain enumeration.</li></ul><h4>5. Advanced Techniques</h4><p>There exist two levels of techniques which can be used beyond traditional subdomain enumeration tools:</p><ul><li>Principal DNS servers with incorrect settings are vulnerable to DNS Zone Transfers that will provide complete domain records. Command: dig axfr @nameserver example.com</li><li>Subdomains can be obtained from Certificate Transparency Logs through the utilization of ctfr and certspotter tools. Example: ctfr -d example.com</li><li>The Wayback Machine allows users to scrape saved pages in order to identify references for subdomains. Website: <a href="https://archive.org/web/">https://archive.org/web/</a></li><li>Experts conduct the DNSSEC Walk to take advantage of DNSSEC setups that help discover domain subdomains. Tool: dnswalk</li></ul><h4>7. Frameworks</h4><p>Multiple tools are integrated into unified interfaces by certain frameworks that provide users with simplified enumeration capabilities.</p><ul><li><strong>Recon-ng: </strong>A recon framework with modules for subdomain enumeration. Website: <a href="https://recon-ng.com/">https://recon-ng.com</a></li><li><strong>Gobuster: </strong>A versatile tool for directory and subdomain enumeration. Command: gobuster dns -d example.com -w wordlist.txt</li><li><strong>Aquatone: </strong>Enables users to both detect and obtain screenshots of domain subdomains through its user interface. Command: aquatone-discover -d example.com</li></ul><h4>Conclusion</h4><p>Organizations benefit greatly from subdomain enumeration because it reveals their entire attack surface during security assessments. The choice between passive and active techniques in assessment depends on the current security position of the target environment. Security researchers and penetration testers reach efficient subdomain vulnerability analysis through proper tools and established methodologies.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5fefe74f1d83" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bug Bounty Hunting: Automatic Vulnerability Discovery Using Fuzzers]]></title>
            <link>https://medium.com/@NiaziSec/bug-bounty-hunting-automatic-vulnerability-discovery-using-fuzzers-6da56581c8ae?source=rss-171b87d2579------2</link>
            <guid isPermaLink="false">https://medium.com/p/6da56581c8ae</guid>
            <category><![CDATA[web-testing]]></category>
            <category><![CDATA[bug-bounty-hunter]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-program]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <dc:creator><![CDATA[Muhammad Abdullah Niazi]]></dc:creator>
            <pubDate>Sun, 16 Feb 2025 06:38:32 GMT</pubDate>
            <atom:updated>2025-02-16T06:38:32.533Z</atom:updated>
            <content:encoded><![CDATA[<h4>Comprehensive Guide for Bug Hunters</h4><p>Manual testing stands as the best initial approach toward new targets because it helps discover concealed weaknesses and acquire fresh information about security principles. Covering big applications with manual testing proves to be time-intensive along with being inefficient. Leading bug bounty hunters implement automation across their whole bug-hunting process because of its value in reconnaissance and vulnerability scanning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/0*CnUyjKRTD2FxkcVQ.png" /><figcaption><a href="https://portswigger.net/burp/documentation/desktop/tools/intruder/uses/fuzzing">https://portswigger.net/burp/documentation/desktop/tools/intruder/uses/fuzzing</a></figcaption></figure><p>Fuzzing stands as an exceptionally useful automation method for identifying numerous vulnerabilities during short periods of time. This article explains how fuzzing functions for web application vulnerability testing while demonstrating two essential tools Burp Intruder and Wfuzz to strengthen your security bug analysis. Web applications undergo fuzzing by receiving multiple odd-seeming and poorly formatted input data to check for odd behavior in their output. The system should activate previously unforeseen application responses including program crashes memory leaks and known vulnerabilities like SQL injection (SQLi) and Cross-Site Scripting (XSS) and authentication bypass. Many organizations use fuzzing as their main cybersecurity tool and the majority of Common Vulnerabilities and Exposures (CVE) entries emerge through fuzzing tests. The technique that emerged for binary exploitation purposes has evolved into being essential for testing web security platforms today.</p><h4>How Web Fuzzers Work</h4><p>Web fuzzers accomplish their task by using malicious payloads at various application entry points where data enters the system. These injection points could be:</p><ul><li>URL parameters</li><li>Form fields</li><li>HTTP headers</li><li>JSON/XML input fields</li></ul><p>The tool generates these payloads which then the fuzzer sends to the target application for analysis of responses. Response codes and content length and delays during communication assist in detecting security weaknesses.</p><p><strong>Example: </strong>Wfuzz functions as a widely used open-source tool that automatically conducts payload injection tasks. A standard command for conducting URL payload fuzzing appears as follows:</p><pre>$ wfuzz -w common_paths.txt http://example.com/FUZZ</pre><p>The command uses common_paths.txt to replace FUZZ with all its entries when sending multiple requests for response assessment against the server.</p><p>Example output:</p><pre>000000004: 200 20 L 2904 W 227381 Ch &quot;secure&quot;</pre><p>The server’s response of 200 OK indicates that /secure represents an accessible endpoint on the target device.</p><h3>Steps to Fuzz a Web Application</h3><p><strong>Step 1: Identify Injection Point</strong>s: Application fuzzing deployment requires users to first pinpoint all locations where web applications accept data input. Analyze all places where the server processes user input including form inputs and URL parameters together with header fields.</p><ul><li>Testing <strong>Insecure Direct Object References (IDOR)</strong>:</li><li>$ wfuzz -w ids.txt <a href="http://example.com/view_inbox?user_id=FUZZ">http://example.com/view_inbox?user_id=FUZZ</a></li><li>Testing <strong>XSS Vulnerabilities</strong>:</li><li>$ wfuzz -w xss_payloads.txt <a href="http://example.com/search?q=FUZZ">http://example.com/search?q=FUZZ</a></li></ul><p><strong>Step 2: Choose a Payload List: </strong>Creating successful fuzzing requires using a high-quality wordlist. Recommended payload lists include:</p><ul><li><strong>SecLists</strong> by Daniel Miessler: <a href="https://github.com/danielmiessler/SecLists/">GitHub</a></li><li><strong>Big List of Naughty Strings</strong> by Max Woolf: <a href="https://github.com/minimaxir/big-list-of-naughty-strings/">GitHub</a></li><li><strong>FuzzDB</strong>: <a href="https://github.com/fuzzdb-project/fuzzdb/">GitHub</a></li></ul><p>Random data generation should be done through scripts or through the combination of special characters as a method to find encoding vulnerabilities.</p><p><strong>Step 3: Analyze Results: </strong>The output from your fuzzing operation needs a thorough assessment to detect any unpredictable results. Look for:</p><ul><li>Three abnormal HTTP status messages include 200 OK,403 Forbidden, and 500 Internal Server Error.</li><li>The execution of SQL injection payload will result in longer response times.</li><li>The content displays field changes not matching expected program behaviors or shows information disclosures differently.</li></ul><p>The presence of an IDOR vulnerability exists when the page returns 200 OK with ?user_id=2 while it should allow only user_id=1.</p><h4>Advanced Fuzzing Techniques</h4><p><strong>1. Brute-Forcing Authentication: </strong>Wfuzz serves as a tool for brute-forcing basic authentication credentials when protecting a page.</p><pre>$ wfuzz -w passwords.txt -H &quot;Authorization: Basic FUZZ&quot; http://example.com/admin</pre><p><strong>2. Fuzzing API Endpoints: </strong>Modern applications rely on APIs, which are also vulnerable to fuzzing, which helps discover undocumented API endpoints.</p><pre>$ wfuzz -w api_endpoints.txt -u http://example.com/api/FUZZ</pre><p><strong>3. Customizing Payloads: </strong>generates random strings for fuzzing input validation mechanisms.</p><pre>$ cat /dev/random | tr -dc &#39;A-Za-z0-9!@#$%^&amp;*()&#39; | head -c 20 &gt; payloads.txt</pre><h4>Best Practices for Fuzzing</h4><ul><li>Request throttling should be used to stop generating an excessive number of server requests by adding time-based delays.</li><li>Begin all tests by first getting written permission from the relevant authorities. The fusion of manual testing with automated testing should consist of using automated components for efficiency and applying manual validation controls to confirm results.</li><li>The reporting of vulnerability discovery needs documented evidence stored in records.</li></ul><h4>Conclusion</h4><p>Web vulnerability discovery depends heavily on the effective fuzzing approach. Security researchers can screen for IDOR, XSS and SQLi and authentication bypass problems through automated payload injection by using Burp Intruder and Wfuzz tools. Always practice ethical hacking with respect to legal guidelines as well as specific disclosure protocols.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6da56581c8ae" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bug Bounty Hunting: Web Vulnerability (API Testing)]]></title>
            <link>https://medium.com/@NiaziSec/bug-bounty-hunting-web-vulnerability-api-testing-96a49acc4f35?source=rss-171b87d2579------2</link>
            <guid isPermaLink="false">https://medium.com/p/96a49acc4f35</guid>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[api-testing]]></category>
            <category><![CDATA[bug-bounty-hunter]]></category>
            <category><![CDATA[bug-bounty-program]]></category>
            <dc:creator><![CDATA[Muhammad Abdullah Niazi]]></dc:creator>
            <pubDate>Sun, 16 Feb 2025 06:32:46 GMT</pubDate>
            <atom:updated>2026-06-03T17:27:21.437Z</atom:updated>
            <content:encoded><![CDATA[<h4>API Testing: Techniques, Bypasses, and Exploits</h4><p>Software development relies on APIs (Application Programming Interfaces) because they provide a base for controlled and efficient application for data sharing. Most applications depend on APIs to achieve communication and data sharing through their programmed interfaces for all social media applications, online purchases, and third-party service integration. This article examines various API forms and their operational process while demonstrating their vital importance for operations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/0*Ock4nIuQI4XcBbM7.png" /><figcaption><a href="https://portswigger.net/web-security/api-testing">https://portswigger.net/web-security/api-testing</a></figcaption></figure><p>Programmers utilize APIs as a way to retrieve ready-made resources so they can develop advanced functionalities instead of creating new options from scratch.</p><p>Through its public API platform, Twitter enables developers to perform tweet data retrieval and new tweet posting functions and conduct various other commands. Twitter’s public API provides developers with this API request to retrieve database contents from their network:</p><pre>GET /1.1/statuses/show.json?id=210462857140252672<br>Host: api.twitter.com</pre><p>The command retrieves a particular tweet by using its exclusive identification number. The API responds with JSON data that offers a structured and readable way for data transfer.</p><h3>JSON Data Format</h3><p>Most Application Programming Interfaces provide JSON (JavaScript Object Notation) data that uses key-value pair structures. The Twitter API delivers responses in the following JSON format:</p><pre>{<br>  &quot;created_at&quot;: &quot;Wed Oct 10 20:19:24 +0000 2018&quot;,<br>  &quot;id&quot;: 1050118621198921728,<br>  &quot;text&quot;: &quot;To make room for more expression, we will now count all emojis as equal...&quot;,<br>  &quot;user&quot;: {<br>    &quot;id&quot;: 6253282,<br>    &quot;name&quot;: &quot;Twitter API&quot;,<br>    &quot;screen_name&quot;: &quot;TwitterAPI&quot;<br>  }<br>}</pre><p>The ability to embed objects and lists within JSON structures makes it an adaptable format that most API response protocols employ.</p><h3>API Authentication</h3><p>API systems usually need authentication systems to manage user access permissions. Users demonstrate their identity through access tokens until they combine them with authentication headers or cookies. The server uses API to decide which components and assets the user has permission to access.</p><h4>Types of APIs</h4><p>API developments use multiple different architectural designs that fulfill unique purposes. REST APIs stand as one of three main API varieties.</p><p><strong>1. REST APIs (Representational State Transfer): </strong>The REST APIs stand as the dominant API architecture in current market use. REST APIs depend on HTTP methods including GET and POST and PUT and DELETE.</p><ul><li><strong>GET</strong> — Retrieve data</li><li><strong>POST</strong> — Create new resources</li><li><strong>PUT</strong> — Update existing resources</li><li><strong>DELETE</strong> — Remove resources</li></ul><p>Example REST API endpoints:</p><pre>GET https://api.twitter.com/1.1/statuses/show<br>POST https://api.twitter.com/1.1/statuses/destroy<br>POST https://api.twitter.com/1.1/statuses/retweet</pre><p><strong>2. SOAP APIs (Simple Object Access Protocol): </strong>SOAP functions as an older API protocol that implements XML as its communication standard. Enterprise applications together with legacy systems continue to employ SOAP as their communication protocol. A SOAP request has an appearance as follows:</p><pre>&lt;DeleteBucket xmlns=&quot;http://doc.s3.amazonaws.com/2006-03-01&quot;&gt;<br>  &lt;Bucket&gt;quotes&lt;/Bucket&gt;<br>  &lt;AWSAccessKeyId&gt;AKIAIOSFODNN7EXAMPLE&lt;/AWSAccessKeyId&gt;<br>  &lt;Timestamp&gt;2006-03-01T12:00:00.183Z&lt;/Timestamp&gt;<br>&lt;/DeleteBucket&gt;</pre><p>Requests and responses from SOAP operations use XML as their communication format, and WSDL (Web Services Description Language) files that describe the API structure are included as well.</p><p><strong>3. GraphQL APIs: </strong>GraphQL emerged after REST to deliver a more flexible application programming interface (API) method. GraphQL operates through one endpoint while users are required to initiate their data requests.</p><p>Example GraphQL query:</p><pre>query {<br>  shop {<br>    name<br>    primaryDomain {<br>      url<br>    }<br>  }<br>}</pre><p>The output keeps only relevant fields from the request therefore decreasing the amount of redundant data transferred. GraphQL allows users to use mutations for implementing data creation and modification.</p><p>Example GraphQL mutation:</p><pre>mutation {<br>  customerCreate(input: { firstName: &quot;John&quot;, lastName: &quot;Tate&quot;, email: &quot;john@example.com&quot; }) {<br>    customer {<br>      id<br>    }<br>  }<br>}</pre><h4>API-Centric Applications</h4><ul><li>Applications today use APIs for their underlying structure more than for simple data exchange. APIs become the primary channels through which client-side applications acquire their data instead of delivering complete HTML documents.</li><li>The mobile application of Facebook obtains post content directly from API queries instead of loading HTML documents. The implementation of API-centric architecture enables mobile applications to access web application data through their backend system which promotes faster development.</li></ul><h4>Security Risks of API-Centric Applications</h4><p>Active usage of APIs provides network access to expanded amounts of data together with additional functionality points that heighten security vulnerabilities. Two key security issues among others that affect systems are the exposure of important data and technical flaws in application functionality.</p><h4>API Vulnerability Hunting</h4><p>Reconnaissance (Recon) Techniques, Use open-source tools for API testing:</p><ul><li><strong>Postman</strong> serves as a solution to develop and control API requests.</li><li><strong>GraphQL Playground</strong> — GraphQL query testing with autocompletion.</li><li><strong>ZAP GraphQL Add-on</strong> executes GraphQL introspection while creating automated test queries through its system.</li><li><strong>Clairvoyance</strong> enables users to map GraphQL API structures even when the introspection feature is disabled.</li></ul><p><strong>API Enumeration Strategies:</strong></p><ul><li>The company_name API should be searchable on Google for public documentation. Check for internal API documents through Swagger integration when searching for inurl:swagger.</li><li>The system deduces new endpoint matches based on detected patterns (/posts/1234, /posts/1236 to /posts/1235).</li><li>The analysis of JavaScript source code combined with GitHub repositories allows users to find API endpoints that developers have not documented.</li><li>Run API discovery scans against hidden endpoints by using the wordlists found at <a href="https://gist.github.com/yassineaboukir/">https://gist.github.com/yassineaboukir/.</a> Verify the presence of past API versions (also using /api/v1/…, while the latest version shows at /api/v2/…) since out-of-date versions may still contain unsecured vulnerabilities.</li></ul><h4>Testing API Security</h4><p><strong>1. Broken Access Control &amp; Information Leaks: </strong>The authentication system of APIs depends on access tokens but fails to validate tokens properly which results in unwanted user access permission.</p><ul><li>API tokens can be either too easily predicted or completely invalidating other security protocols even when they should automatically expire.</li><li>API endpoints fail to implement adequate authorization controls that would determine whether non-admins can reach administrative data.</li><li>API endpoints use different methods to specify delete functions because they contain inconsistent access control permissions (/delete vs. DELETE).</li><li><strong>Example vulnerability: </strong>An endpoint that sends private user tokens to the response enables successful account hijacking for attackers.</li></ul><h4><strong>Testing techniques:</strong></h4><ul><li>You should create multiple accounts that belong to various privilege levels. Verify endpoint functionality while the access tokens have been disabled.</li><li>The testing process must evaluate GET and POST in addition to PUT and DELETE HTTP methods.</li><li>User identifiers in API requests should be modified to detect possible Insecure Direct Object References (IDOR). The GraphQL mutation tests need to evaluate whether low-privileged users can edit restricted data sets.</li></ul><h4>2. Rate-Limiting Issues</h4><ul><li>An API system without rate limits enables attackers to accomplish:</li><li>Brute-force authentication endpoints. Users can enumerate system data through automatic ID number guessing. The system allows unauthorized access to extract large quantities of confidential data.</li></ul><h4><strong>Example attack:</strong></h4><ul><li>API endpoint: GET /api/v2/user_emails/52603991338963203244</li><li>No rate limit → attacker brute-forces valid email IDs.</li></ul><p><strong>Testing technique: </strong>The tester submits between 100 to 200 requests at a quick pace through Burp Intruder or curl tools. Check if the system blocks requests through rate-limiting mechanisms at visitor, user, and administrator authentication levels.</p><h4>3. Technical Bugs in APIs</h4><ul><li>Security problems that affect traditional web services can arise due to bad practices in validating API inputs.</li><li>The API becomes vulnerable to SQL Injection attacks due to its acceptance of straight SQL queries.</li><li>The Server-Side Request Forgery (SSRF) occurs when an API contains endpoints that fetch external URLs.</li><li>The occurrence of modifications during simultaneous API endpoint operations is known as Race Conditions.</li><li>API vulnerability to path traversal exists when it reveals file system paths that lead to sensitive information such as (../../etc/passwd).</li><li>A serialization vulnerability is present if the API receives XML data. Similarly, an XML External Entity occurs when the API handles serialized XML input.</li><li>The machine accepts remote code execution attacks through user-submitted executables.</li><li>An API security flaw exists when user content gets displayed without proper data filtering in API responses.</li><li><strong>Testing techniques: </strong>API requests must accept malicious payloads through their injection methods. The API input needs fuzzing to detect validation vulnerabilities. Assess both normal and abnormal data that API returns during every response check.</li></ul><h4>API Security Considerations</h4><p>Since APIs serve as top targets for cyberattacks security measures become essential for protection. Best practices include:</p><ul><li><strong>Authentication &amp; Authorization</strong> — Using OAuth tokens or API keys</li><li>API abuse prevention occurs through rate limiting which controls the amount of API requests received.</li><li><strong>Encryption</strong> — Securing data transmission with HTTPS</li><li>The GraphQL feature of Introspection should remain disabled in order to stop unauthorized users from exploring the API.</li></ul><h4>Conclusion</h4><p>API developers and business stakeholders need to master the understanding of API structures together with security measures regardless of their choice between REST, SOAP, and GraphQL. Technology advancement will continue to rely on APIs as fundamental components for designing software development of the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96a49acc4f35" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>