<?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 Puspojit Biswas on Medium]]></title>
        <description><![CDATA[Stories by Puspojit Biswas on Medium]]></description>
        <link>https://medium.com/@pisecurityit?source=rss-3fab99dd2cd7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4-68Gx4uV-p83BuU1vGxbA.jpeg</url>
            <title>Stories by Puspojit Biswas on Medium</title>
            <link>https://medium.com/@pisecurityit?source=rss-3fab99dd2cd7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 21:32:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pisecurityit/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[DVAPI Walkthrough: OWASP API Security Top 10 (2023)]]></title>
            <link>https://medium.com/@pisecurityit/dvapi-walkthrough-owasp-api-security-top-10-2023-aeb6cd604d76?source=rss-3fab99dd2cd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/aeb6cd604d76</guid>
            <category><![CDATA[api-penetration-testing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[jwt-authentication]]></category>
            <category><![CDATA[owasp-api-security-top-10]]></category>
            <dc:creator><![CDATA[Puspojit Biswas]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 06:03:25 GMT</pubDate>
            <atom:updated>2026-11-09T06:03:25.863Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Welcome to the DVAPI walkthrough. The DVAPI (Damn Vulnerable API) lab provides a series of challenges and exercises related to the top 10 API security risks identified by OWASP. These challenges are designed to test our knowledge and skills in identifying and mitigating common security vulnerabilities in API implementations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pr_MpUurlTXpp-1-BxNafg.png" /></figure><p>The goal of this walkthrough is to set up the lab locally, explore the application, identify security vulnerabilities, and capture the flags by completing the challenges.</p><h3>Lab Overview</h3><ul><li><strong>Lab Name:</strong> DVAPI (Damn Vulnerable API)</li><li><strong>Repository:</strong> <a href="https://github.com/payatu/DVAPI">https://github.com/payatu/DVAPI</a></li><li><strong>Technologies:</strong> Node.js, MongoDB, etc.</li><li><strong>Tools:</strong> Docker, Burp Suite/Caido, Web Browser, JWT_Tool, etc.</li><li><strong>Focus Area:</strong> <a href="https://api-security.owasp.org/editions/2023/en/0x00-header/">OWASP API Security TOP 10 (2023)</a></li></ul><h3>Lab Installation in Local Server</h3><p>Before proceeding with the installation, make sure Git, Docker, and Docker Compose are installed on your server. For this setup, I used a dedicated Debian server running in VMware to host the lab and accessed the application from a Kali Linux machine connected to the same VMware NAT network.</p><ul><li><strong>Clone the lab repository to the local server:</strong><br><em>git clone </em><a href="https://github.com/payatu/DVAPI.git">https://github.com/payatu/DVAPI.git</a><em><br>cd ./DVAPI/</em></li><li><strong>Run the lab instance:</strong><br><em>docker compose up -d</em></li><li><strong>Verify that the containers are running:</strong><br><em>docker ps</em></li><li><strong>The lab is now available at:</strong><br><em>http://192.168.166.135:3000/</em></li></ul><h3>Prerequisites</h3><p>Let’s visit <a href="http://192.168.166.135:3000/register">http://192.168.166.135:3000/register</a> to create a new user with a username<em> </em>and <em>password </em>in DVAPI. Go to <a href="http://192.168.166.135:3000/login">http://192.168.166.135:3000/login</a> to login to the server.</p><p>🚀 <em>Let’s solve the challenges and find the flags…….</em></p><h3><strong>API1:2023 Broken Object Level Authorization</strong></h3><p><strong>Challenge Description:</strong><br>Drop off during a CTF challenge? No problem. Store a secret note on your profile to track your progress and resume where you left off.</p><p><strong>Steps to Get the Flag:</strong></p><p>Visit the created user profile by browsing <a href="http://192.168.166.135:3000/profile">http://192.168.166.135:3000/profile</a> while capturing the requests in the Burp Suite proxy. Find that there is an API request as <strong><em>GET /api/getNote?username=&lt;YOUR_USERNAME&gt; HTTP/1.1. </em></strong>Send it to Burp’s Repeater. Let’s change the <em>username </em>to <em>admin </em>and send it. The flag is discovered in the response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*duN1zAjmXLaP-OzsDgMzfQ.png" /><figcaption>Fig.: BOLA flag revealed in the admin note.</figcaption></figure><p><strong>⛳ The flag is:<br></strong>flag{bola_15_ev3rywh3r3}</p><h3><strong>API2:2023 Broken Authentication</strong></h3><p><strong>Challenge Description:</strong><br>Admin has a challenge for you. Admin says anyone who can log in with their account will get some surprise. Can you find out the surprise?</p><p><strong>Steps to Get the Flag:</strong></p><p>Visit <a href="http://192.168.166.135:3000/profile">http://192.168.166.135:3000/profile</a> while capturing the requests in the Burp Suite proxy. Find that there is an API request as <strong><em>GET /api/getNote?username=&lt;YOUR_USERNAME&gt; HTTP/1.1. </em></strong>Send it to Burp’s Repeater.</p><p>Let’s grab the JWT token from the HTTP request.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*8PqgcW-VpX5jquyDW8gceA.png" /><figcaption>Fig.: JWT token in the /api/getNote endpoint.</figcaption></figure><p>If we decode the JWT token, we find that the token algorithm is &#39;HS256,&#39; where the “<em>isAdmin</em>” value is &#39;false&#39;.<em> </em>I used <a href="https://github.com/ticarpi/jwt_tool">JWT_Tool</a> to decode the JWT token.</p><pre>jwt_tool &quot;eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VySWQiOiI2YWVhMjkzZTE1Njk3YmJlMTRmMmFmYjEiLCJ1c2VybmFtZSI6InNoZXJsb2NrIiwiaXNBZG1pbiI6ImZhbHNlIiwiaWF0IjoxNzk0MTE1NjM0fQ.wYD43eclPiaJxDqjod9a9vHmisQI1vgX7hxlzu3A87I&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/894/1*U71tPIdXWrlYeIaYjBZyog.png" /><figcaption>Fig.: decoded JWT with jwt_tool.</figcaption></figure><p>Let’s decode the secret of the JWT token.</p><pre>jwt_tool &quot;eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VySWQiOiI2YWVhMjkzZTE1Njk3YmJlMTRmMmFmYjEiLCJ1c2VybmFtZSI6InNoZXJsb2NrIiwiaXNBZG1pbiI6ImZhbHNlIiwiaWF0IjoxNzk0MTE1NjM0fQ.wYD43eclPiaJxDqjod9a9vHmisQI1vgX7hxlzu3A87I&quot; -C -d /usr/share/seclists/Passwords/scraped-JWT-secrets.txt </pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b5qb4vv2GMjZw-NqkfhPvw.png" /><figcaption>Fig.: JWT token secret decoded.</figcaption></figure><p>The decoded secret is ‘<em>secret123</em>’.</p><p>In the Burp’s Repeater, I am using a ‘<em>JSON Web Tokens’</em> extension to edit the JWT and send it. Let’s change the ‘username’ value to &#39;admin&#39; and the ‘isAdmin’ value to ‘true’ and sign the JWT with our discovered secret, that <em>secret123</em>. Send the request and notice that the flag has been revealed in the response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*747UkfiVLVjyuPthjLQCPA.png" /><figcaption>Fig.: flag revealed via JWT token manipulation.</figcaption></figure><p><strong>⛳ The flag is:<br></strong>flag{aBus1ng_w34K_s3cR3TTT}</p><h3><strong>API3:2023 Broken Object Property Level Authorization</strong></h3><p><strong>Challenge Description:</strong><br>Ever wished there was a cheat code to top the scoreboard?</p><p>Steps to Get the Flag:</p><p>Let’s register (<a href="http://192.168.166.135:3000/register">http://192.168.166.135:3000/register</a>) a new user while intercepting the request in the Burp Suite. Add an extra parameter “score” with the value 99999 and forward it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8rDR5nWT98EtRRxsMk47sw.png" /><figcaption>Fig.: new user vicitm10 has been created with score 99999.</figcaption></figure><p>Let’s log in (<a href="http://192.168.166.135:3000/login">http://192.168.166.135:3000/login</a>) to the website and visit the scores by visiting the <a href="http://192.168.166.135:3000/scoreboard">http://192.168.166.135:3000/scoreboard</a> URL.</p><p>Find the <em>GET /api/scores HTTP/1.1</em> request in the Burp HTTP History and notice that the newly created user is a top scorer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ouXgKzy4QFHbzsHYs-bRnQ.png" /><figcaption>Fig.: new user on top of the scoreboard.</figcaption></figure><p>Check the flag at the bottom of the HTTP response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sj9JaAyHUbGaRanB-RjhVw.png" /><figcaption>Fig.: flag revealed in the /api/scores API endpoint when the user is the top scorer.</figcaption></figure><p><strong>⛳ The flag is:<br></strong>flag{br0k3n_oBj3cT_Pr0p3rTy_L3v3L_Auth0RiS4Ti0N}</p><h3><strong>API4:2023 Unrestricted Resource Consumption</strong></h3><p><strong>Challenge Description:</strong><br>Do you know that you can customize your profile? Try it out and make your profile stand out among others.</p><p>Steps to Get the Flag:</p><p>Visit the user profile (<a href="http://192.168.166.135:3000/profile">http://192.168.166.135:3000/profile</a>) and upload a 100MB-size image as a profile picture while capturing the requests in Burp Suite. This upload process will consume more resources than usual.</p><p>Find the <em>POST /api/profile/upload HTTP/1.1</em> request and wait for a few moments. After a while, the flag is visible in the HTTP response of that request.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*afwJ4ylrDX7OPRx3Yp3NHA.png" /><figcaption>Fig.: flag revealed when the process consumes many resources.</figcaption></figure><p><strong>⛳ The flag is:<br>flag{file_size_is_important}</strong></p><h3><strong>API5:2023 Broken Function Level Authorization</strong></h3><p><strong>Challenge Description:</strong><br>DVAPI has many users. You can see other’s profile and others can see yours. What could go wrong here? Right? Right???</p><p><strong>Steps to Get the Flag:</strong></p><p>Visit <a href="http://192.168.166.135:3000/user/sherlock">http://192.168.166.135:3000/user/</a>&lt;YOUR_USERNAME&gt; (in my case, <a href="http://192.168.166.135:3000/user/sherlock">http://192.168.166.135:3000/user/sherlock</a>) and capture the request in the Burp Suite. Find the <em>GET /api/user/&lt;YOUR_USERNAME&gt; HTTP/1.1</em> (in my case, <em>GET /api/user/sherlock HTTP/1.1</em>) request and send it to the Burp’s repeater.</p><p>Browse <a href="http://192.168.166.135:3000/scoreboard">http://192.168.166.135:3000/scoreboard</a> and find that there are some other users like <em>Alice,</em> <em>Bob,</em> <em>Admin, </em>and others. In the request, replace the username with one of the other users. I am using <em>Alice </em>here. Change the HTTP method to DELETE and send the request. Notice that the user has been deleted without authorization, and we got the flag in the response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*60-HLI4S12fq5Hawp5Z2gQ.png" /><figcaption>Fig.: user Alice has been deleted without authorization.</figcaption></figure><p><strong>⛳ The flag is:<br></strong>flag{n0_fUncTi0N_L3v3L_aUtH???}</p><h3><strong>API6:2023 Unrestricted Access to Sensitive Business Flows</strong></h3><p><strong>Challenge Description:</strong><br>DVAPI is a people first applicaiton. We are keen on knowing your requests through submit ticket function. Maybe it’ll help you find the flag !!!</p><p><strong>Steps to Get the Flag:</strong></p><p>Let’s create a new ticket by clicking the ticket icon near the profile picture and capture the request in the Burp. Send it to the Burp Intruder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HD6hOdzm0ksAcYaBvYi6TQ.png" /><figcaption>Fig.: new ticket creation.</figcaption></figure><p>Let’s perform the sniper brute force attack with null payloads while selecting the payload configuration as ‘continue indefinitely.&#39; This process will create a huge number of tickets continuously.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pvj4DRAg4moUhdwSjRTBvw.png" /><figcaption>Fig.: creation of huge no. of tickets by brute forcing.</figcaption></figure><p>After a few moments of time, notice that the length is changing. Check on that changed length request and find that the flag has been revealed in the HTTP response due to the unrestricted access of a business flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*El6H1AA5lezECGdhzuJiyg.png" /><figcaption>Fig.: flag revealed due to the unrestricted access of a business flow.</figcaption></figure><p><strong>⛳ The flag is:<br></strong>flag{n0_r4t3_L1m1T?}</p><h3><strong>API7:2023 Server Side Request Forgery</strong></h3><p><strong>Challenge Description:</strong><br>DVAPI is using a function to set SecretNote for your user through a link/url. Try to learn more about SSRF and capture the flag!!!</p><p><strong>Steps to Get the Flag:</strong></p><p>Visit the profile (<a href="http://192.168.166.135:3000/profile">http://192.168.166.135:3000/profile</a>) and update the note with a link while capturing the request in the Burp.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QRp9ijXlMTDmmqXLjKF7eQ.png" /><figcaption>Fig.: note updating with URL.</figcaption></figure><p>Find the <em>POST /api/addNoteWithLink HTTP/1.1</em> request and send to the Burp Intruder. Change the URL as <a href="http://127.0.0.1/">http://127.0.0.1:80/</a>. Perform a sniper brute force attack with the common open ports in a system available here: <a href="https://pastebin.com/raw/gZwcs0hM">https://pastebin.com/raw/gZwcs0hM</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rUv1w75qSwXAVAW16mtEQg.png" /><figcaption>Fig.: sniper brute forcing the ports in 127.0.0.1</figcaption></figure><p>Notice that for port number 8443, the flag has been revealed in the HTTP response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*74XcgofDaaiCT1TtXesKVQ.png" /><figcaption>Fig.: SSRF flag revealed for 127.0.0.1’s 8443 port.</figcaption></figure><p><strong>⛳ The flag is:<br></strong>flag{55RF_c4n_wR3AK_h4v0c}</p><h3><strong>API8:2023 Security Misconfiguration</strong></h3><p><strong>Challenge Description:</strong><br>The Developers at DVAPI are lazy which has led to a misconfigured system. Find the misconfiguration and submit the flag!!!</p><p>Steps to Get the Flag:</p><p>Browse <a href="http://192.168.166.135:3000/challenges">http://192.168.166.135:3000/challenges</a> and capture the requests in the Burp proxy. Find any API endpoint with a JWT token (I am using the <em>GET /api/profile HTTP/1.1</em> request) and send it to the repeater.</p><p>Remove the JWT signature and send the request. Notice that the server is proving a detailed error message with our expected flag.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9wKzF9Xr-8ynNDnUGVcDmA.png" /><figcaption>Fig.: flag revealed in the detailed error message due to security misconfiguration.</figcaption></figure><p><strong>⛳ The flag is:<br></strong>flag{St4cK_tR4c3_eRR0R}</p><h3><strong>API9:2023 Improper Inventory Management</strong></h3><p>Challenge Description:<br>There was a data leak at DVAPI. People found out there are 12 Challenges and not 10, What do you think?</p><p>Steps to Get the Flag:</p><p>Visit <a href="http://192.168.166.135:3000/challenges">http://192.168.166.135:3000/challenges</a> and capture the request in the Burp Suite. Find the <em>POST /api/allChallenges HTTP/1.1</em> request and send it to the Burp Repeater.</p><p>View the source code of <a href="http://192.168.166.135:3000/challenges">http://192.168.166.135:3000/challenges</a> and find that there is a hidden parameter as ‘unreleased’ with value 1 for the <em>/api/allChallenges</em> request.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1019/1*DUK_OYAAjB9Xj4PVLsRiKw.png" /><figcaption>Fig.: hidden ‘unreleased’ parameter found in the source code.</figcaption></figure><p>Let’s change the <em>“released”:1</em> to <em>“unreleased”:1</em> in the Repeater of the <em>/api/allChallenges</em> request and send it. It reveals the hidden challenge11 and challenge12. The challenge12 description contains the flag.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VcNUfQYziOYwuTWPE6muSg.png" /><figcaption>Fig.: unreleased challenges revealed with flag.</figcaption></figure><p><strong>⛳ The flag is:<br></strong>flag{a553Ts_m4N4g3m3NT_g0n3_wR0ng}</p><h3><strong>API10:2023 Unsafe Consumption of APIs</strong></h3><p><strong>Challenge Description:</strong><br>API’s used at the Authentication of the application does not look safe, can you test it and get the flag??</p><p>Steps to Get the Flag:</p><p>Log out and visit <a href="http://192.168.166.135:3000/login">http://192.168.166.135:3000/login</a> to log in as the ‘a<em>dmin’</em> user while capturing the request in Burp Suite. Send the <em>POST /api/login HTTP/1.1</em> request to the Burp Repeater.</p><p>As the used DB is a NoSQL database (MongoDB), let’s try NoSQL injection in the login JSON data as follows:</p><pre>{&quot;username&quot;:&quot;admin&quot;,&quot;password&quot;:{&quot;$ne&quot;:&quot;221B&quot;}}</pre><p>Notice that the authentication has been successful and we got the flag.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FZc7X3gyEd8AbedxAk1SlA.png" /><figcaption>Fig.: NoSQL injection in the login page as admin to get the flag.</figcaption></figure><h3>Conclusion</h3><p>Working through the DVAPI lab was a great hands-on experience that helped me better understand how common API security vulnerabilities work in practice. Rather than just reading about different vulnerabilities, I got the opportunity to explore API endpoints, inspect HTTP requests and responses, manipulate parameters, and see how small security weaknesses can lead to bigger issues.</p><p>A big thanks to <strong>Payatu</strong> for creating and sharing this lab with the security community.</p><p>I hope this walkthrough helps others who are starting their journey into API penetration testing. Thanks for reading, and happy hacking!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aeb6cd604d76" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[vAPI Walkthrough: OWASP API Security Top 10 (2019)]]></title>
            <link>https://medium.com/@pisecurityit/vapi-walkthrough-owasp-api-security-top-10-2019-69503a2bcdd6?source=rss-3fab99dd2cd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/69503a2bcdd6</guid>
            <category><![CDATA[owasp-api-security-top-10]]></category>
            <category><![CDATA[api-penetration-testing]]></category>
            <category><![CDATA[cybersecurity-training]]></category>
            <category><![CDATA[jwt-authentication]]></category>
            <dc:creator><![CDATA[Puspojit Biswas]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 06:00:42 GMT</pubDate>
            <atom:updated>2026-11-09T06:00:42.489Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Welcome to the vAPI walkthrough. In this walkthrough, we will explore vAPI, an intentionally vulnerable API security lab. vAPI is a Vulnerable Adversely Programmed Interface, which is a self-hostable API that mimics OWASP API Top 10 scenarios through exercises.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*naXjA-5TEdu0nNuviaHgtg.png" /></figure><p>The goal of this walkthrough is to install the lab in a local environment, access the lab, and find the security flaws and challenge flags.</p><h3>Lab Overview</h3><ul><li><strong>Lab Name:</strong> vAPI (Vulnerable Adversely Programmed Interface)</li><li><strong>Repository:</strong> <a href="https://github.com/roottusk/vapi">https://github.com/roottusk/vapi</a></li><li><strong>Technologies:</strong> PHP, MySQL, etc.</li><li><strong>Tools:</strong> Docker, Postman, Burp Suite / Caido, etc.</li><li><strong>Focus Area:</strong> <a href="https://api-security.owasp.org/editions/2019/en/0x11-t10/">OWASP API Security Top 10 (2019)</a></li></ul><h3>Lab Installation in Local Server</h3><p>Before installation, make sure that we have already installed git, docker.io, and docker-compose in the server. In my case, I used a dedicated local Debian server in VMware for lab installation and accessed that lab from a Kali Linux machine in that same VMware NAT network.</p><ul><li><strong>Clone the lab repository to the local server:</strong><br><em>git clone https://github.com/roottusk/vapi.git<br>cd ./vapi/</em></li><li><strong>Run the lab instance:</strong><br><em>docker compose up -d</em></li><li><strong>Verify that the containers are running:</strong><br><em>docker ps</em></li><li><strong>The lab is now available at:</strong><br><em>http://192.168.166.135:8000/vapi/</em></li></ul><h3>Importing vAPI Collection &amp; Environment into Postman</h3><p>To import the vAPI collection and environment in Postman, visit <a href="https://github.com/roottusk/vapi/tree/master/postman">https://github.com/roottusk/vapi/tree/master/postman</a> and download them. Import both of them to the Postman and select the environment as <strong><em>vAPI_ENV</em></strong><em>.</em></p><p>Now we need to change the <strong><em>host </em></strong>variable value with the lab host value as <strong><em>192.168.166.135:8000</em></strong>, as displayed in the following screenshot. (<em>If you want to access the lab from the same machine, there is no need to change the host variable.</em>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/922/1*fLWVW5OLV15ip9cCtVV3tA.png" /><figcaption>Fig.: host variable has been changed to 192.168.166.135:8080.</figcaption></figure><blockquote>To pass the HTTP requests in the Caido/Burp Suite proxy, we need to enable ‘<strong><em>Use custom proxy configuration</em></strong>’ in Postman’s <strong><em>App Settings → Proxy </em></strong>option<em>.</em></blockquote><p>🚀 <em>Let’s solve the challenges and find the flags……..</em></p><h3>API-1: Broken Object Level Authorization</h3><p><strong>Challenge Description:</strong><br>You can register yourself as a User , Thats it ….or is there something more?</p><p><strong>Steps to Get the Flag:</strong></p><p>Let’s create a user called ‘<strong><em>victim</em></strong>’ in the lab with the ‘<em>API1</em> → <strong><em>POST Create User’</em></strong> request in the collection. The<strong><em> ‘id’</em></strong> of the user victim is ‘<strong><em>5’.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mho7RLMao_H-17eR7NQ_fg.png" /><figcaption>Fig.: user victim has been created with id ‘5’</figcaption></figure><p>In the ‘<em>API1</em> → <strong><em>GET Get User</em></strong>’ request, change the ‘<strong><em>auth_id</em></strong>’ value to ‘<strong><em>1</em></strong>’ and send the request. We get the flag of this challenge in the response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VWusmbuE8dxYBBZgszKDpg.png" /><figcaption>Fig.: flag discovered in the course value for user id 1.</figcaption></figure><p><strong>⛳ The flag is:</strong> <br>flag{api1_d0cd9be2324cc237235b}</p><h3>API-2: Broken Authentication</h3><p><strong>Challenge Description:</strong><br>We don’t seem to have credentials for this, How do we login? (There’s something in the Resources Folder given to you.)</p><p><strong>Steps to Get the Flag:</strong></p><p>In the ‘<strong><em>API2 → POST User Login</em></strong>’ request, enter the test <em>email </em>and <em>password, s</em>end the request, and capture it in the Caido proxy. Let’s send the request to Caido’s Auomate. We need to download the provided user email and password wordlist (creds.csv) by visiting <a href="https://github.com/roottusk/vapi/blob/master/Resources/API2_CredentialStuffing/creds.csv">https://github.com/roottusk/vapi/blob/master/Resources/API2_CredentialStuffing/creds.csv</a>. Let’s create a different list of user emails and passwords from the provided <strong><em>creds.csv</em></strong> file.</p><p>Let’s perform a &#39;parallel&#39; brute force attack on the user login for the user email and password with the provided credentials list. We need to disable the URL encoding while performing this login brute force attack.</p><p>We found 2 valid login credentials.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jzK44hWBbzkAhOEO15axtA.png" /><figcaption>Fig.: successful brute force attack in the user login.</figcaption></figure><p>Let’s log in with the email address as <a href="/service/mailto:hauck.aletha@yahoo.com"><strong><em>hauck.aletha@yahoo.com</em></strong></a> and the password as <strong><em>kU-wDE7r </em></strong>in Postman. The token of this successful login will be applied in the ‘<strong><em>API2 → GET Get Details</em></strong>’ request. Send the request, and we get the flag in the response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fy3yiYkgMLbsVyLP0Fm8bw.png" /><figcaption>Fig.: flag discovered for the second challenge.</figcaption></figure><p><strong>⛳ The flag is:</strong><br>flag{api2_6bf2beda61e2a1ab2d0a}</p><h3>API-3: Excessive Data Exposure</h3><p><strong>Challenge Description:</strong><br>We have all been there, right? Giving away too much data and the Dev showing it. Try the Android App in the Resources folder.</p><p><strong>Please Note: </strong><br><em>To get the flag of this challenge, we need to modify a provided APK file. Due to the lack of Android Studio setup and enough resources, I skipped this challenge.</em></p><h3>API-4: Lack of Resources &amp; Rate Limiting</h3><p><strong>Challenge Description:</strong><br>We believe OTPs are a great way of authenticating users and secure too if implemented correctly!</p><p><strong>Steps to Get the Flag:</strong></p><p>Send the ‘API4 → POST Mobile Login’ request and notice that it successfully sent a 4-digit OTP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q8lRpNhl4m8qbiCYSPZdRA.png" /><figcaption>Fig.: 4-digit OTP sent successfully to the mobile no.</figcaption></figure><p>Send the ‘<strong><em>API4 → POST Verify OTP</em></strong>’ request with test 4-digit OTP <strong><em>9999</em></strong>, capture the request in Caido, and send it to Automate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q8lRpNhl4m8qbiCYSPZdRA.png" /><figcaption>Fig.: 4-digit OTP supplied to test.</figcaption></figure><p>Let’s perform the ‘<em>sequential</em>’ brute force in the OTP field with numbers from <em>1000 </em>to <em>9999 </em>and notice that we found a valid OTP as <strong><em>1872</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FDtwKgCv_6T9ATJqQc8uZA.png" /><figcaption>Fig.: valid OTP found by brute forcing.</figcaption></figure><p>Verify the OTP in Postman and send the ‘API4 → GET Get Details’ request. Notice that we received the flag in the response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-CGYI576stM1oj6a5AOh-A.png" /><figcaption>Fig.: flag discovered for API4 challenge.</figcaption></figure><p><strong>⛳ The flag is:</strong><br>flag{api4_ce696239323ea5b2d015}</p><h3>API-5: Broken Function Level Authorization</h3><p><strong>Challenge Description:</strong><br>You can register yourself as a User. Thats it or is there something more? (I heard admin logins often but uses different route)</p><p><strong>Steps to Get the Flag:</strong></p><p>Send the ‘<strong><em>API5 → POST Create User</em></strong>’ request to create a new user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3YFjM0zdja31V-vfMdUCKw.png" /><figcaption>Fig.: a new user ‘testuser2’ has been created with id 2.</figcaption></figure><p>Modify the ‘<strong><em>API5 → Get User</em></strong>’ request from <em>/vapi/api5/user/{{api5_id}} </em>to<em> </em>/vapi/api5/users and send it. Notice that we discovered the flag for this challenge in the response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E-dCWXhkYUsZwdmnQb_1eA.png" /><figcaption>Fig.: URL modified to get all the user details.</figcaption></figure><p><strong>⛳ The flag is:</strong><br>flag{api5_76dd990a97ff1563ae76}</p><h3>API-6: Mass Assignment</h3><p>Challenge Description:<br>Welcome to our store. We will give you credits if you behave nicely. Our credit management is super secure.</p><p><strong>Steps to Get the Flag:</strong></p><p>As the challenge is about the mass assignment, and it was telling us about the credit in the description, it is quite obvious that we may add our own credits by ourselves. While creating a new user by sending the ‘<strong><em>API6 → POST Create User</em></strong>’ request, let’s add an extra parameter ‘credit’ with value ‘1000’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7CHaqRiFtKyFw6ZNydhCZQ.png" /><figcaption>Fig.: victim2 user has been created with 1000 credits.</figcaption></figure><p>The user has been created successfully. Let’s send the ‘<strong><em>API6 → GET Get User</em></strong>’ request and find the flag in the response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nm6zumenHF68fOeEofiTHA.png" /><figcaption>Fig.: flag found in the newly created user details.</figcaption></figure><p><strong>⛳ The flag is:</strong><br>flag{api6_afb969db8b6e272694b4}</p><h3>API-7: Security Misconfiguration</h3><p><strong>Challenge Description:</strong><br>Hey, its an API right? so we ARE expecting Cross Origin Requests . We just hope it works fine.</p><p><strong>Steps to Get the Flag:</strong></p><p>Create a new user by using the ‘<strong><em>API7 → POST Create User</em></strong>’ request.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9XG5BWapFtMCCRhy9LUBQw.png" /><figcaption>Fig.: new victim3 user created.</figcaption></figure><p>Send the ‘<strong><em>API7 → GET User Login</em></strong>’ request to log in as the newly created ‘<em>victim3</em>’ user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AeezMsPnxfCejIlnszKQoQ.png" /><figcaption>Fig.: victim3 user logged in successfully.</figcaption></figure><p>Let’s add a new HTTP header ‘Origin’ with value ‘example.com’ in the ‘API7 → Get Key’ request and send it. The flag is found in the HTTP response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jHaTfvGJcTiyrs21zd6HQA.png" /><figcaption>Fig.: flag discovered by adding a new Origin header.</figcaption></figure><p><strong>⛳ The flag is:<br></strong>flag{api7_e71b65071645e24ed50a}</p><h3>API-8: Injection</h3><p>Challenge Description:<br>I think you won’t get credentials for this. You can try to log in, though.</p><p>Steps to Get the Flag:</p><p>Add <strong><em>admin’ OR 1=1 — — </em></strong>in the username variable in the ‘<strong><em>API8 → POST User Login</em></strong>’ request and send it. Notice that we are successfully logged in as <em>admin </em>by exploiting the SQL injection vulnerability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bru6942rVP5eXLWGkAG1xg.png" /><figcaption>Fig.: log in successfully as admin by SQL injection.</figcaption></figure><p>Let’s send the ‘<strong><em>API8 → GET Get Secret</em></strong>’ request and find the secret (flag) in the HTTP response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iPUMFGjkp21xrM3128ieYw.png" /><figcaption>Fig.: admin secret revealed as a flag for the challenge.</figcaption></figure><p><strong>⛳ The flag is:<br></strong>flag{api8_509f8e201807860d5c91}</p><h3>API-9: Improper Assets Management</h3><p><strong>Challenge Description:</strong><br>Hey Good News!!!!! We just launched our v2 API :)</p><p><strong>Steps to Get the Flag:</strong></p><p>As the challenge description mentioned about the new version of the API as v2, the old version v1 might still be in use.</p><p>By exploring the API endpoint ‘<strong><em>API9 → v2 → POST Login</em></strong>’, I noticed that the v2 version of it has a rate-limit security implementation to protect against brute force attacks. In the HTTP response, the <em>X-Ratelimit-Limit</em> header is found with the value <em>5</em>, while the <em>X-Ratelimit-Remaining</em> value is decreasing by 1 from <em>5</em> with an invalid attempt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5iRYrIySv02CP3BdabbUqQ.png" /><figcaption>Fig.: X-Ratelimit-Remaining value has decreased to 3 after 2 invalid attempts.</figcaption></figure><p>After all the 5 invalid attempts, we are getting the <em>500 — Internal Server Error</em> and restricting us from performing any invalid attempts for a while.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j85LvBD-aS4uziIip2rynA.png" /><figcaption>Fig.: 500 Internal Server Error after 5 invalid login attempts.</figcaption></figure><p>But I discovered that the v1 version has no rate-limit implementation. Let’s modify the ‘<strong><em>API9 → v2 → POST Login’ </em></strong>from <em>/vapi/api9/v2/user/login</em> to <em>/vapi/api9/v1/user/login </em>and send the request while capturing it in the <em>Caido</em>. Let’s send the request to <em>Caido’s Automate</em> and perform a sequential brute force with the numbers from 1000 to 9999.</p><p>By filtering the response length, we found the value of ‘<strong><em>pin</em></strong>’ as &#39;1655&#39;, and the flag has been revealed in the HTTP response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s8AKXWmCLJ3vy1OGv2t-Mg.png" /><figcaption>Fig.: successful brute force in the v1 login endpoint to get the pin and flag.</figcaption></figure><p><strong>⛳ The flag is:<br></strong>flag{api9_81e306bdd20a7734e244}</p><h3>API-10: Insufficient Logging &amp; Monitoring</h3><p>Challenge Description:<br>Nothing has been logged or monitored. You caught us :( !</p><p>Steps to Get the Flag:</p><p>Send the ‘<strong><em>API10 → GET Get Flag</em></strong>’ request and get the flag in the HTTP response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k673Lpyic7hNjtr7Jlt5Bg.png" /><figcaption>Fig.: flag discovered for the challenge API10.</figcaption></figure><p><strong>⛳ The flag is:<br></strong>flag{api10_5db611f7c1ffd747971f}</p><h3>Arena — JustWeakToken</h3><p><strong>Steps to Get the Flag:</strong></p><p>Let’s create a new user by using the ‘<strong><em>Arena → JustWeakToken → POST Create User</em></strong>’ request.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4cl2g3yQ-XOQXJ2Xy3WXHA.png" /><figcaption>Fig.: new user created as named ‘victim5’</figcaption></figure><p>Send the ‘<strong><em>Arena → JustWeakToken → GET Get User’ </em></strong>request to get the details of the user while capturing the request in Burp Suite. Let’s send the request to Burp’s Repeater.</p><p>Manipulate the JWT token to change the role from ‘<em>user</em>’ to ‘<em>admin</em>’ and change the ‘<em>alg</em>’ value with ‘<em>none</em>’. Send the request, and we discovered the flag.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zk61w7Op0y4tw_0rQ5MCVQ.png" /><figcaption>Fig.: flag discovered by ‘none’ signing algorithm attack and user role manipulation.</figcaption></figure><p><strong>⛳ The flag is:<br></strong>flag{jwt_qnopkkt3owsxndk083v1}</p><h3>Arena—ServerSurfer</h3><p><strong>Challenge Solution:</strong></p><p>In the ‘<strong><em>Arena → ServerSurfer → GET Get Data</em></strong>’ request, change the ‘url’ parameter value with an <a href="https://app.interactsh.com/">Interact-sh</a> webhook URL: <a href="http://blvxxqcqltgdlvcyspucz4xrburysn9fr.oast.fun/">http://blvxxqcqltgdlvcyspucz4xrburysn9fr.oast.fun</a> and send the request.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XTvOoKQBfLVeRh7cgHxpDQ.png" /><figcaption>Fig.: data received from interact-sh webhook.</figcaption></figure><p>We received the base64-encoded data in the response as</p><pre>{<br>    &quot;success&quot;: &quot;true&quot;,<br>    &quot;data&quot;: &quot;PGh0bWw+PGhlYWQ+PC9oZWFkPjxib2R5PnJmOW5zeXJ1YnJ4NHpjdXBzeWN2bGRndGxxY3F4eHZsYjwvYm9keT48L2h0bWw+&quot;<br>}</pre><p>Let’s decode the base64-encoded data by using the CyberChef web tool.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ELKxs5pHhO9Tlprj1xZmUw.png" /><figcaption>Fig.: base64-encoded data decoded using the CyberChef web tool.</figcaption></figure><p>The decoded data is:</p><pre>&lt;html&gt;&lt;head&gt;&lt;/head&gt;&lt;body&gt;rf9nsyrubrx4zcupsycvldgtlqcqxxvlb&lt;/body&gt;&lt;/html&gt;</pre><p>Now, if we check the Interact-sh web tool dashboard, we find the same HTTP response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qx8B04Ph91arwFvsp4F0Kg.png" /><figcaption>Fig.: HTTP response from Interact-sh.</figcaption></figure><p>The key takeaway is that the vAPI application fetches and displays the content returned by the URL supplied through the GET parameter. In this case, we used a simple string to demonstrate the behavior. However, an attacker could potentially provide a malicious URL to make the server send requests to unintended resources. This behavior indicates a Server-Side Request Forgery (SSRF) vulnerability.</p><blockquote><em>Please Note: This challenge does not have a flag.</em></blockquote><h3>Arena — StickyNotes</h3><p>Challenge Solution:</p><p>In the ‘<strong><em>Arena → StickyNotes → POST Store a Note</em></strong>’ request, mention an XSS payload as <em>&lt;img src=x onerror=alert(1)&gt;</em> the note and send the request.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LRCIoTqDSRWBYBICoZSxkA.png" /><figcaption>Fig.: XSS payload stored as note.</figcaption></figure><p>Now, send the ‘<strong><em>Arena → StickyNotes → GET Get Notes</em></strong>’ request while the ‘<em>format</em>’ parameter’s value is ‘<em>html</em>’ and find the flag in the HTTP response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hCyxDVoxtWRRQB4-YmSKzw.png" /><figcaption>Fig.: StickeyNotes challenge flag discovered.</figcaption></figure><p><strong>⛳ The flag is:</strong><br>flag{xss_e2rghxe4164cc2472xwb}</p><h3>Conclusion</h3><p>The vAPI lab was a valuable hands-on experience for understanding the OWASP API Security Top 10 (2019). By setting up the application locally and working through its challenges, I was able to see how common API security weaknesses can be identified and exploited in a controlled environment.</p><p>A big thanks to <strong>roottusk </strong>for creating and sharing this lab with the security community.</p><p>I hope this walkthrough helps other learners who are beginning their journey into API security and want to gain practical experience with the OWASP API Security Top 10.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69503a2bcdd6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>