<?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 Greg Gibson on Medium]]></title>
        <description><![CDATA[Stories by Greg Gibson on Medium]]></description>
        <link>https://medium.com/@greg-gibson?source=rss-f786d83bd003------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0QZLI-2Li9ZGxSkY92NfNg.jpeg</url>
            <title>Stories by Greg Gibson on Medium</title>
            <link>https://medium.com/@greg-gibson?source=rss-f786d83bd003------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 12:41:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@greg-gibson/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[Critical Bug Bounty Reports: Part 1]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://infosecwriteups.com/critical-bug-bounty-reports-part-1-6fd9aef4b486?source=rss-f786d83bd003------2"><img src="https://cdn-images-1.medium.com/max/1984/1*2Fd7ENUVc11JrQde8ibfVg.jpeg" width="1984"></a></p><p class="medium-feed-snippet">Short Write-Ups On P1/Critical Bugs I&#x2019;ve Submitted to Bounty Programs</p><p class="medium-feed-link"><a href="https://infosecwriteups.com/critical-bug-bounty-reports-part-1-6fd9aef4b486?source=rss-f786d83bd003------2">Continue reading on InfoSec Write-ups »</a></p></div>]]></description>
            <link>https://infosecwriteups.com/critical-bug-bounty-reports-part-1-6fd9aef4b486?source=rss-f786d83bd003------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fd9aef4b486</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bugcrowd]]></category>
            <category><![CDATA[vulnerability-management]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <dc:creator><![CDATA[Greg Gibson]]></dc:creator>
            <pubDate>Sun, 11 Jul 2021 08:13:33 GMT</pubDate>
            <atom:updated>2021-07-11T08:13:33.587Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Reflected XSS Through Insecure Dynamic Loading]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://infosecwriteups.com/reflected-xss-through-insecure-dynamic-loading-dbf4d33611e0?source=rss-f786d83bd003------2"><img src="https://cdn-images-1.medium.com/max/921/1*SZxEvYsp2L1OyT9yx_pJqQ.png" width="921"></a></p><p class="medium-feed-snippet">Finding A Unique and Complex Payload To Load Remote Scripts</p><p class="medium-feed-link"><a href="https://infosecwriteups.com/reflected-xss-through-insecure-dynamic-loading-dbf4d33611e0?source=rss-f786d83bd003------2">Continue reading on InfoSec Write-ups »</a></p></div>]]></description>
            <link>https://infosecwriteups.com/reflected-xss-through-insecure-dynamic-loading-dbf4d33611e0?source=rss-f786d83bd003------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbf4d33611e0</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <category><![CDATA[bugcrowd]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[hacker]]></category>
            <dc:creator><![CDATA[Greg Gibson]]></dc:creator>
            <pubDate>Sun, 11 Jul 2021 07:12:53 GMT</pubDate>
            <atom:updated>2021-07-11T07:12:53.542Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Executing CSRF With Phone Validation]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://infosecwriteups.com/executing-csrf-with-phone-validation-103c525dd310?source=rss-f786d83bd003------2"><img src="https://cdn-images-1.medium.com/max/640/1*IJK27pBimW2rAfGZVnTWqw.png" width="640"></a></p><p class="medium-feed-snippet">How to Programmatically Harvest the OTP</p><p class="medium-feed-link"><a href="https://infosecwriteups.com/executing-csrf-with-phone-validation-103c525dd310?source=rss-f786d83bd003------2">Continue reading on InfoSec Write-ups »</a></p></div>]]></description>
            <link>https://infosecwriteups.com/executing-csrf-with-phone-validation-103c525dd310?source=rss-f786d83bd003------2</link>
            <guid isPermaLink="false">https://medium.com/p/103c525dd310</guid>
            <category><![CDATA[exploit]]></category>
            <category><![CDATA[csrf]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Greg Gibson]]></dc:creator>
            <pubDate>Fri, 04 Jun 2021 20:49:02 GMT</pubDate>
            <atom:updated>2021-06-07T05:12:43.095Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Exploiting Imported Libraries to Bypass WAF]]></title>
            <link>https://infosecwriteups.com/exploiting-imported-libraries-to-bypass-cloudflare-waf-7aed99186c5a?source=rss-f786d83bd003------2</link>
            <guid isPermaLink="false">https://medium.com/p/7aed99186c5a</guid>
            <category><![CDATA[xss-filter-bypass]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Greg Gibson]]></dc:creator>
            <pubDate>Tue, 14 Jul 2020 21:00:57 GMT</pubDate>
            <atom:updated>2021-09-09T01:31:16.923Z</atom:updated>
            <content:encoded><![CDATA[<h4>Turning a P5 Content Injection into P3 Reflected XSS</h4><p>A private program I previously had no success with announced a new scope item — their primary landing page <a href="http://www.redacted.com/service/?zipCode=12345">www.redacted.com/*</a>. The original scope included only their mobile apps and while I’ve had some success with mobile targets, my expertise is finding slightly more obscure logic bugs in web apps.</p><p>After performing my usual basic recon, nothing of interest jumped out at me as this was a mostly static site, delivering content on the company’s various business offerings with redirects to currently out of scope subdomains. I went to work searching for a page with URL parameters and discovered entering a US Zip Code into one search box would redirect to www.redacted.com/service/?zipCode=12345 with the value reflected into the &lt;input&gt; box. Time to start testing.</p><h3>Initial Foothold — HTML Content Injection</h3><p>I quickly discovered this &lt;input&gt; field lacked the <strong>most critical </strong>sanitization, allowing an attacker to escape from the <em>value </em>attribute using “ and further allowing the tag to be closed using &gt;. At this point I’ve identified a vulnerability, but Content Injection understandably is a P5, worthy of a single point and no bounty payout as there is no actual security impact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*QwacgZJhmBm4zIeLMKyTsQ.jpeg" /><figcaption>The zipCode parameter is vulnerable to content injection and possible further exploit. Shown here are several attributes of the input tag now floating as text just below the input box.</figcaption></figure><p>I would rather sit on this injection for a month trying to escalate it than submit a P5 and move on. Immediately I went for the kill shot and tried injecting <strong>“&gt;&lt;script&gt;alert(1);&lt;/script&gt;</strong>. I don’t typically have high expectations in this scenario, especially for a company of this size and stature but it’s certainly worth a try. However, as I expected the response was a block.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/683/1*OcbPhTP8TilGC_Sx-zXleA.jpeg" /><figcaption>403 block response from a suspected Cloudflare WAF.</figcaption></figure><h3>Time For Recon</h3><p>Developing a list of HTML tags, attributes, and events that are allowed through the filter will enable me to attempt to craft an injection string that will result in a successful exploit. Although <strong>&lt;script&gt;</strong>, <strong>&lt;style&gt;</strong>, and <strong>&lt;img&gt;</strong> are all blocked, <strong>&lt;a&gt;</strong>, <strong>&lt;svg&gt;</strong>, <strong>&lt;object&gt;</strong>, and <strong>&lt;div&gt;</strong> are allowed. Checking attributes of each allowed tag, <strong>&lt;svg src=&gt;</strong> and <strong>&lt;object data=&gt;</strong> result in blocks — nothing will come easy. I should also mention <strong>alert()</strong> and <strong>confirm()</strong> are blocked but <strong>prompt() </strong>is not. Additionally inline style returns 403 as well. Moving to events, seemingly all are blocked but by chance I noticed a rather obscure event, <strong>onwebkitanimationstart </strong>manages to get through!</p><p>Every example I found to trigger XSS with this event involved the use of inline style. One such example from <a href="https://medium.com/u/a90d4c9f2c62">Brute Logic</a> is shown below:</p><pre>&lt;style&gt; <br>div{width:100px;height:100px;-webkit-animation-name:n;}@-webkit-keyframes n{}<br>&lt;/style&gt;</pre><pre>&lt;vulntag attrib=&quot;&quot;onwebkitanimationstart=alert(9)&gt;</pre><pre>&lt;div&gt;<br>    <br>&lt;!-- <a href="http://twitter.com/brutelogic">@brutelogic</a> --&gt;</pre><p>Since I can’t inject style, I ran a search in the Inspector console for webkit-animation to see if there were any existing classes I could leverage and discovered the <a href="https://getbootstrap.com/docs/4.0/components/progress/">Bootstrap Progress</a> bar. Specifically, the Animated Stripes feature through the classes class=&quot;progress-bar progress-bar-striped progress-bar-animated&quot; would act as the trigger.</p><h3>Moment of Truth</h3><p>With a plan in place I began crafting a new injection string to test, using the Bootstrap documentation to create the wrapper div and the component div.</p><pre>https://www.redacted.com/service/?zipCode=&quot;&gt;&lt;div class=progress&gt;&lt;div onwebkitanimationstart=prompt(document.domain) class=&quot;progress-bar progress-bar-striped progress-bar-animated&quot; role=&quot;progressbar&quot; aria-valuenow=&quot;75&quot; aria-valuemin=&quot;0&quot; aria-valuemax=&quot;100&quot;&gt;</pre><p>After a few nights of progressive work identifying the vulnerability, conducting recon to determine what could bypass the filter, and finally leveraging existing libraries to provide the necessary trigger I successfully demonstrated an impact and escalated a P5 content injection to P3 Reflected Cross Site Scripting! You can see the webkit-animation in the blue progress bar just below the input box.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/1*vivhFXc6vUZeLPuyQzkEYA.jpeg" /><figcaption>A successful XSS injection using Bootstrap’s Progress bar.</figcaption></figure><h3>Takeaway</h3><p>There is always an inherent risk to not immediately reporting a vulnerability in that another hacker can beat you to it. However, as mentioned earlier I’m not interested in the reward (or lack thereof) that comes from identifying a vulnerability without demonstrable impact for one major reason: Cyber Security is about managing risk; if you cannot <strong>demonstrate </strong>a security impact, your vulnerability will not be prioritized for remediation, leaving the vulnerability unpatched for a malicious actor to abuse.</p><p>If you get stuck trying to bypass a WAF or other filter with your injection, always look through the source code to see what the target provides — often you’ll find the very thing you need for a successful exploit is already loaded into the page!</p><p>I’m not very active on Social Media, but you can find me on <a href="https://www.linkedin.com/in/greg-gibson/">LinkedIn</a> or hanging out in various security Slack or Discord servers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7aed99186c5a" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/exploiting-imported-libraries-to-bypass-cloudflare-waf-7aed99186c5a">Exploiting Imported Libraries to Bypass WAF</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>
    </channel>
</rss>