<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Findings on Mazin Ahmed</title><link>https://mazinahmed.net/tags/findings/</link><description>Recent content in Findings on Mazin Ahmed</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 08 Apr 2016 00:00:00 +0000</lastBuildDate><atom:link href="https://mazinahmed.net/tags/findings/index.xml" rel="self" type="application/rss+xml"/><item><title>Google UI-Redressing Bug That Discloses the User's Email Address</title><link>https://mazinahmed.net/blog/google-ui-redressing-bug-that-discloses-email-addresses/</link><pubDate>Fri, 08 Apr 2016 00:00:00 +0000</pubDate><guid>https://mazinahmed.net/blog/google-ui-redressing-bug-that-discloses-email-addresses/</guid><description>&lt;hr&gt;&#10;&lt;p&gt;In this post, I will discuss an exciting bug affecting Google Blogger. This security bug has been left undiscovered since around 2007.&lt;/p&gt;&#10;&lt;p&gt;The bug allows an attacker to trick the victim into revealing his email address using UI-redressing techniques.&lt;/p&gt;&#10;&lt;h1 id="background" class="relative group"&gt;Background &lt;span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100"&gt;&lt;a class="group-hover:text-primary-300 dark:group-hover:text-neutral-700" style="text-decoration-line: none !important;" href="#background" aria-label="Anchor"&gt;#&lt;/a&gt;&lt;/span&gt;&lt;/h1&gt;&lt;p&gt;We always see a header on blogs that are hosted on Google Blogger that looks like the following:&lt;/p&gt;&#10;&lt;p&gt;For unauthenticated users:&#10;&#10;&#10;&#10;&#10;&#10;&#10;&#10; &#10; &#10;&lt;figure&gt;&lt;img src="https://mazinahmed.net/uploads/assets/static/6f1d5c56-0c8c-41c9-9237-424e0de454eb.png" alt="" class="mx-auto my-0 rounded-md" /&gt;&#10;&lt;/figure&gt;&#10;&lt;/p&gt;</description></item><item><title>Bypassing Google Password Alert with One Line of Code</title><link>https://mazinahmed.net/blog/bypassing-google-password-alert/</link><pubDate>Sat, 25 Jul 2015 00:00:00 +0000</pubDate><guid>https://mazinahmed.net/blog/bypassing-google-password-alert/</guid><description>&lt;p&gt;Google Password Alert has become very popular recently. It&amp;rsquo;s practical and a great defensive way to mitigate phishing damages against Google users.&lt;/p&gt;&#10;&lt;p&gt;It has been bypassed several times as soon as it arrived, and Google has patched all the known techniques.&#10;After hearing that Google had patched all known techniques, I thought about testing it to see how long it would take me to bypass it.&lt;/p&gt;&#10;&lt;p&gt;My first idea was to use document.write and encode the phishing page in Unicode, and see the results. The method worked successfully in v1.12.&lt;/p&gt;</description></item><item><title>Facebook Messenger Multiple CSRF Vulnerabilities</title><link>https://mazinahmed.net/blog/facebook-messenger-multiple-csrf/</link><pubDate>Tue, 09 Jun 2015 00:00:00 +0000</pubDate><guid>https://mazinahmed.net/blog/facebook-messenger-multiple-csrf/</guid><description>&lt;hr&gt;&#10;&lt;p&gt;In this post, I will demonstrate the findings of multiple interesting cross-site request forgery vulnerabilities I identified on Facebook. These vulnerabilities allow an attacker to force the victim to do various actions.&lt;/p&gt;&#10;&lt;p&gt;In April 2015, Facebook officially launched messenger.com, a stand-alone messenger for the web. After hearing about the launch, I started to test it in my spare time.&lt;/p&gt;&#10;&lt;hr&gt;&#10;&lt;h1 id="sending-unrestricted-messages-to-any-user-via-csrf" class="relative group"&gt;Sending Unrestricted Messages to Any User via CSRF &lt;span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100"&gt;&lt;a class="group-hover:text-primary-300 dark:group-hover:text-neutral-700" style="text-decoration-line: none !important;" href="#sending-unrestricted-messages-to-any-user-via-csrf" aria-label="Anchor"&gt;#&lt;/a&gt;&lt;/span&gt;&lt;/h1&gt;&lt;p&gt;Using this issue, I could force any user to send messages to other users without the user&amp;rsquo;s knowledge.&lt;/p&gt;</description></item><item><title>W3 Total Cache's W3TotalFail Vulnerability That Leads to Full Defacement (CVE-2014-9414)</title><link>https://mazinahmed.net/blog/w3-total-fail/</link><pubDate>Thu, 11 Dec 2014 00:00:00 +0000</pubDate><guid>https://mazinahmed.net/blog/w3-total-fail/</guid><description>&lt;hr&gt;&#10;&lt;p&gt;In this post, I will be talking about a critical vulnerability that affects W3 Total Cache, the most popular WordPress plugin in the world. Most major companies use W3 Total Cache, which provides a vital service that every WordPress website needs.&lt;/p&gt;&#10;&lt;h3 id="overview-on-w3-total-cache" class="relative group"&gt;Overview on W3 Total Cache &lt;span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100"&gt;&lt;a class="group-hover:text-primary-300 dark:group-hover:text-neutral-700" style="text-decoration-line: none !important;" href="#overview-on-w3-total-cache" aria-label="Anchor"&gt;#&lt;/a&gt;&lt;/span&gt;&lt;/h3&gt;&lt;p&gt;&amp;ldquo;W3 Total Cache improves your site&amp;rsquo;s user experience by increasing server performance, reducing the download times, and providing transparent content delivery network (CDN) integration.&amp;rdquo;&lt;/p&gt;</description></item><item><title>Session Hijacking in Instagram Mobile App via MITM Attack [0-DAY]</title><link>https://mazinahmed.net/blog/session-hijacking-in-instagram-mobile/</link><pubDate>Sat, 26 Jul 2014 00:00:00 +0000</pubDate><guid>https://mazinahmed.net/blog/session-hijacking-in-instagram-mobile/</guid><description>&lt;hr&gt;&#10;&lt;p&gt;In this post, I will share a new critical issue I identified on Instagram Mobile App. During my tests on their Android app, I set up a lab to pentest the app. Then, I started using the app on my phone and monitoring the traffic on the network using Wireshark, looking for evidence of unencrypted data that goes through the network or a technique to make this data unencrypted (if it were encrypted). As soon as I logged into my account on my phone, Wireshark captured unencrypted data that went through HTTP. This data includes the pictures the target is watching, the target&amp;rsquo;s session cookies, the username, and the ID.&lt;/p&gt;</description></item><item><title>My Story with Onavo (Acquired by Facebook)</title><link>https://mazinahmed.net/blog/my-story-with-onavo/</link><pubDate>Mon, 09 Jun 2014 00:00:00 +0000</pubDate><guid>https://mazinahmed.net/blog/my-story-with-onavo/</guid><description>&lt;hr&gt;&#10;&lt;p&gt;When I was checking the Facebook WhiteHat page, I realized that they added a new target to the scope: Onavo.&lt;/p&gt;&#10;&lt;p&gt;&#10;&#10;&#10;&#10;&#10;&#10;&#10; &#10; &#10;&lt;figure&gt;&lt;img src="https://mazinahmed.net/uploads/assets/static/ea205f89-3c1b-4439-aca1-7f4f7641f0e3.png" alt="" class="mx-auto my-0 rounded-md" /&gt;&#10;&lt;/figure&gt;&#10;&lt;/p&gt;&#10;&lt;p&gt;I downloaded their apps and started to intercept the links that I found.&lt;/p&gt;&#10;&lt;p&gt;One of the links raised an eyebrow. I said to myself that this looks vulnerable.&lt;/p&gt;&#10;&lt;p&gt;The link looks something like this:&#10;&lt;code&gt;http://cf.onavo.com/iphone/mc/deactivate.html?url=https://mazinahmed.net/somethingthatIforget/&amp;amp;seed=1394953248&lt;/code&gt;&lt;/p&gt;&#10;&lt;p&gt;&#10;&#10;&#10;&#10;&#10;&#10;&#10; &#10; &#10;&lt;figure&gt;&lt;img src="https://mazinahmed.net/uploads/assets/static/25c568fb-c3a4-4861-bf08-cf46d9a2b63d.png" alt="" class="mx-auto my-0 rounded-md" /&gt;&#10;&lt;/figure&gt;&#10;&lt;/p&gt;&#10;&lt;p&gt;It seems vulnerable to Open Redirect.&lt;/p&gt;&#10;&lt;p&gt;I executed the link like this:&#10;&lt;code&gt;http://cf.onavo.com/iphone/mc/deactivate.html?url=http://bing.com&amp;amp;seed=1394953248&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>