<?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 Rishu Ranjan on Medium]]></title>
        <description><![CDATA[Stories by Rishu Ranjan on Medium]]></description>
        <link>https://medium.com/@rishuranjanofficial?source=rss-d981ba3dbc86------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*JT-kWDnoRR-jgQLzqlKS6A.jpeg</url>
            <title>Stories by Rishu Ranjan on Medium</title>
            <link>https://medium.com/@rishuranjanofficial?source=rss-d981ba3dbc86------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 13:44:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rishuranjanofficial/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[The 13-Byte Lesson: Why Software Should Never Trust a Number It Didn’t Check | Google Perfetto]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://infosecwriteups.com/the-13-byte-lesson-why-software-should-never-trust-a-number-it-didnt-check-801ab7bfcf80?source=rss-d981ba3dbc86------2"><img src="https://cdn-images-1.medium.com/max/1424/1*4-qAU8nBL36KyFIoLO0VOQ.png" width="1424"></a></p><p class="medium-feed-snippet">A tiny file froze one of Google&#x2019;s most-used engineering tools. The mistake behind it is one almost every developer makes &#x2014; and the fix is&#x2026;</p><p class="medium-feed-link"><a href="https://infosecwriteups.com/the-13-byte-lesson-why-software-should-never-trust-a-number-it-didnt-check-801ab7bfcf80?source=rss-d981ba3dbc86------2">Continue reading on InfoSec Write-ups »</a></p></div>]]></description>
            <link>https://infosecwriteups.com/the-13-byte-lesson-why-software-should-never-trust-a-number-it-didnt-check-801ab7bfcf80?source=rss-d981ba3dbc86------2</link>
            <guid isPermaLink="false">https://medium.com/p/801ab7bfcf80</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Rishu Ranjan]]></dc:creator>
            <pubDate>Mon, 31 Aug 2026 10:07:39 GMT</pubDate>
            <atom:updated>2026-08-31T11:16:47.695Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[JWTweak v2.1: A Guided, Offline Toolkit for Modern JWT Attacks]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://infosecwriteups.com/jwtweak-v2-1-a-guided-offline-toolkit-for-modern-jwt-attacks-d951fa31f964?source=rss-d981ba3dbc86------2"><img src="https://cdn-images-1.medium.com/max/1178/1*yQ3_Ty53v6UbFKMsn9XXwg.png" width="1178"></a></p><p class="medium-feed-snippet">Paste a token, get a full attack plan &#x2014; then execute it, entirely offline.</p><p class="medium-feed-link"><a href="https://infosecwriteups.com/jwtweak-v2-1-a-guided-offline-toolkit-for-modern-jwt-attacks-d951fa31f964?source=rss-d981ba3dbc86------2">Continue reading on InfoSec Write-ups »</a></p></div>]]></description>
            <link>https://infosecwriteups.com/jwtweak-v2-1-a-guided-offline-toolkit-for-modern-jwt-attacks-d951fa31f964?source=rss-d981ba3dbc86------2</link>
            <guid isPermaLink="false">https://medium.com/p/d951fa31f964</guid>
            <category><![CDATA[jwt]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cyber-security-tools]]></category>
            <category><![CDATA[appsec]]></category>
            <dc:creator><![CDATA[Rishu Ranjan]]></dc:creator>
            <pubDate>Tue, 07 Jul 2026 11:35:52 GMT</pubDate>
            <atom:updated>2026-07-07T11:35:52.160Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Credentials Bruteforce Bypass via Password Spraying Attack]]></title>
            <link>https://rishuranjanofficial.medium.com/credentials-bruteforce-bypass-via-password-spraying-attack-cbec82f9a2ca?source=rss-d981ba3dbc86------2</link>
            <guid isPermaLink="false">https://medium.com/p/cbec82f9a2ca</guid>
            <dc:creator><![CDATA[Rishu Ranjan]]></dc:creator>
            <pubDate>Thu, 28 Aug 2025 15:39:00 GMT</pubDate>
            <atom:updated>2025-10-30T08:06:57.875Z</atom:updated>
            <content:encoded><![CDATA[<p>I wrote about Password Spraying Attacks on <a href="https://owasp.org/www-community/attacks/Password_Spraying_Attack">OWASP</a>, where I explained how this technique differs from traditional brute force attacks. In simple terms, Password spraying is a variant of brute force attack methodology employed by malicious actors to gain unauthorized access to a system or application. In this type of attack, the assailant systematically attempts logins by using a list of usernames in conjunction with a single password-often a commonly used or default password. Unlike traditional brute force attacks, where multiple passwords are tried against a single account, password spraying involves trying one password across numerous accounts to evade account lockout mechanisms that would typically be triggered by repeated attempts on a single account. In this blog, I’m sharing the same insights with some additional context for readers of my personal site. Understanding this attack and its mitigations is crucial to building stronger defenses against evolving threats.</p><p>This technique is particularly effective in instances where the application or administrator has established default passwords for new users. The attacker, by leveraging a single password across multiple accounts, aims to exploit instances where users have not changed their default passwords. This underscores the significance of implementing robust password policies, encouraging users to set unique and strong passwords, and regularly updating default passwords to mitigate the risk of password spraying attacks.</p><p>Password spraying underscores the importance of heightened security measures, including the establishment of strong, unique passwords, regular password updates, and vigilant monitoring for anomalous login patterns. Implementing multi-factor authentication (MFA) can further enhance security by adding an additional layer of protection even if passwords are compromised.</p><p>It is crucial for organizations to remain vigilant against password spraying attacks and continually assess and enhance their security protocols to safeguard against evolving cyber threats.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*w0AvXOgYbR8mDHYH.png" /></figure><p>Mitigating the risks associated with password spraying attacks requires a comprehensive and layered approach. Here are some recommended mitigations:</p><p>1. <strong>Username and Password Brute Force Prevention:</strong></p><p>- Implement robust policies to prevent brute force attacks on both usernames and passwords.</p><p>- Monitor and set thresholds for failed login attempts on both fields to detect and respond to suspicious activities promptly.</p><p>2. <strong>Account Lockout Policies:</strong></p><p>- Enforce account lockout policies after a specified number of failed login attempts to hinder attackers from guessing credentials.</p><p>- Carefully configure lockout duration and thresholds to balance security and user convenience.</p><p>3. <strong>CAPTCHA Implementation:</strong></p><p>- Consider implementing CAPTCHA mechanisms to thwart automated password spraying attempts.</p><p>- In scenarios where account lockout is not a feasible option, CAPTCHA provides an additional layer of defense against automated attacks.</p><p>4. <strong>Password Change on First Login:</strong></p><p>- For applications managed by administrators, mandate users to change their passwords on the first login, especially when default passwords are initially assigned.</p><p>- Encourage the use of strong, unique passwords during the password change process.</p><p>5. <strong>Multi-Factor Authentication (MFA):</strong></p><p>- Deploy multi-factor authentication to add an extra layer of security beyond passwords.</p><p>- Implement MFA for both internal and externally facing services to fortify access controls.</p><p>6. <strong>Enhanced Security Education:</strong></p><p>- Conduct regular security awareness training for users to emphasize the importance of setting strong passwords, promptly changing default passwords, and recognizing phishing attempts.</p><p>7. <strong>Regular Password Audits:</strong></p><p>- Periodically audit user accounts to identify and rectify weak or default passwords.</p><p>- Implement processes to prompt users to update their passwords regularly.</p><p>8. <strong>Monitoring and Anomaly Detection:</strong></p><p>- Implement real-time monitoring and anomaly detection to identify unusual patterns in login activity.</p><p>- Establish alerting mechanisms to notify administrators of potential security incidents.</p><p>9. <strong>Continuous Security Assessment:</strong></p><p>- Regularly assess and update security protocols to adapt to evolving threats.</p><p>- Conduct penetration testing to identify vulnerabilities and validate the effectiveness of security measures.</p><p>By adopting a combination of these measures, organizations can significantly reduce the risk of password spraying attacks and enhance the overall security posture of their systems and applications.</p><p><a href="https://owasp.org/www-community/attacks/Password_Spraying_Attack">https://owasp.org/www-community/attacks/Password_Spraying_Attack</a></p><p><em>Originally published at </em><a href="https://www.securethy.com/2025/08/credentials-bruteforce-bypass-via.html"><em>https://www.securethy.com</em></a><em> on August 28, 2025.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cbec82f9a2ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A short story of Content Spoofing to HTML Injection in Apple using Dangling Markup Injection]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://infosecwriteups.com/html-injection-in-itunesconnect-apple-com-3f8a898f21ee?source=rss-d981ba3dbc86------2"><img src="https://cdn-images-1.medium.com/max/1140/1*ZuyavWYlmWTE881DC5nD8g.png" width="1140"></a></p><p class="medium-feed-snippet">Content Spoofing to HTML Injection in Apple. During the recon phase, I found itunesconnect.apple.com, subdomain of apple and after digging</p><p class="medium-feed-link"><a href="https://infosecwriteups.com/html-injection-in-itunesconnect-apple-com-3f8a898f21ee?source=rss-d981ba3dbc86------2">Continue reading on InfoSec Write-ups »</a></p></div>]]></description>
            <link>https://infosecwriteups.com/html-injection-in-itunesconnect-apple-com-3f8a898f21ee?source=rss-d981ba3dbc86------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f8a898f21ee</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Rishu Ranjan]]></dc:creator>
            <pubDate>Sun, 03 Oct 2021 16:31:09 GMT</pubDate>
            <atom:updated>2021-12-08T08:04:12.591Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Stored XSS in Google connected Apps EML, MHT Viewer with Drive]]></title>
            <link>https://rishuranjanofficial.medium.com/stored-xss-in-google-connected-apps-eml-mht-viewer-with-drive-9b16b46d5122?source=rss-d981ba3dbc86------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b16b46d5122</guid>
            <category><![CDATA[google]]></category>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Rishu Ranjan]]></dc:creator>
            <pubDate>Sat, 12 Dec 2020 20:57:32 GMT</pubDate>
            <atom:updated>2020-12-12T21:27:05.856Z</atom:updated>
            <content:encoded><![CDATA[<p>This is the story about a live bug that is still there with Google connected App <strong>EML, MHT Viewer with Drive.</strong> The motive for this blog is to make people aware and avoid using the above mentioned Google connected App.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tTiA2qec-zU5EaoN3A-95Q.png" /></figure><p>The above app will be suggested if you open eml file over the drive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IJkJM_46edFgMo7N3CQIbw.png" /><figcaption>suggested apps for eml file</figcaption></figure><p><strong>Steps to reproduce</strong></p><p>1. Generate the eml file(test.eml) with malicious XSS payloads.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LWCPxXccp0YDLkktFQEdMg.png" /><figcaption>test.eml code</figcaption></figure><p>2. Upload the file to drive and authorize with your google account and open it with <a href="https://www.google.com/url?q=http://mhtviewer.booogle.net&amp;sa=D&amp;usg=AFQjCNGVBfTJCsAzazG5qpCGpvDm4UD-fw">mhtviewer.booogle.net</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6pZggl-MkD5AgA84tE4D7Q.png" /><figcaption>test.eml uploaded on drive</figcaption></figure><p>3. Observe that the malicious JS is executed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3vHwgFFhpk-L-2aBBVsDIg.png" /><figcaption>confirm(document.domain)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mFHNkdc0rhfX2PR5L-kasQ.png" /><figcaption>confirm(document.cookie)</figcaption></figure><p><strong>Attack scenario</strong></p><p>Cross Site Scripting (XSS) on the website also hurts the reputation of the organization as it is possible to tamper with the content of the webpage being shown to the users. <br>Due to its persistent nature, this vulnerability can affect a large number of users. An attacker will be able to easily compromise a bulk of users instead of targeting individual users. In this scenario, an attacker can send malicious email as attachment (eml) file to different users and the victim will open with the suggested vulnerable app and then let the victim to perform the malicious activity on his behalf.</p><p><strong>Google Explanation</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/1*3P1IbrsJUf-nJpGmpwDJ9w.png" /><figcaption>Google Reply</figcaption></figure><p>This is the reply from Google which is valid. I tried to contact the 3rd party App owner but hard luck. Please share this with others to refrain them from using this app. Suggestions are welcome.</p><p>Peace out!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b16b46d5122" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Application Security Assessment using Burp Community Edition | Part — 3| Audit Guidelines |…]]></title>
            <link>https://rishuranjanofficial.medium.com/web-application-security-assessment-using-burp-community-edition-part-3-audit-guidelines-cdf1fd80bacf?source=rss-d981ba3dbc86------2</link>
            <guid isPermaLink="false">https://medium.com/p/cdf1fd80bacf</guid>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[audit]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Rishu Ranjan]]></dc:creator>
            <pubDate>Sun, 28 Jun 2020 15:13:57 GMT</pubDate>
            <atom:updated>2020-06-28T15:13:57.136Z</atom:updated>
            <content:encoded><![CDATA[<h3>Web Application Security Assessment using Burp Community Edition | Part — 3| Audit Guidelines | High Impact Web Vulnerability</h3><h3>Account Takeover via Forgot Password — A Practical Attack Scenario of Host Header Injection</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*PtnHF5pPea5jjPpN88JBNw.png" /></figure><h4><strong>What is Host Header?</strong></h4><p>The Host request header specifies the host and port number of the server to which the request is being sent. By the default port for the service requested (e.g., 443 for an HTTPS URL, and 80 for an HTTP URL) is implied.</p><p>A Host header field must be sent in all HTTP/1.1 request messages. A 400 (Bad Request) status code may be sent to any HTTP/1.1 request message that lacks a Host header field or that contains more than one.</p><h4>Audit Guideline</h4><ol><li>Capture the change password request in the burp community and send the request to the repeater.</li><li>Add one more Host Header with custom domain<strong> </strong>as value<strong> </strong>in the request and send the request.</li><li>Observe the victim will get the password reset mail having link with custom domain and the token. Once the victim click on the link, the attacker will get the link in his web logs.</li></ol><p><strong>Proof of Concept</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-H0nzpTqRM-BR6FUOmy5jw.png" /><figcaption>Original Reset Password link mail</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f6-yHIz56u8t4O6VpVbhyA.png" /><figcaption>Modified reset link request</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AYeEMF7lB7dJQQdF-PdsXA.png" /><figcaption>Reset password link mail with attacker provided domain</figcaption></figure><p><strong>Reference</strong></p><p><a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Host">https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Host</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cdf1fd80bacf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Application Security Assessment using Burp Community Edition | Part — 2| Audit Guidelines |…]]></title>
            <link>https://rishuranjanofficial.medium.com/web-application-security-assessment-using-burp-community-edition-part-2-audit-guidelines-eace9bcbcb9f?source=rss-d981ba3dbc86------2</link>
            <guid isPermaLink="false">https://medium.com/p/eace9bcbcb9f</guid>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Rishu Ranjan]]></dc:creator>
            <pubDate>Sat, 30 Nov 2019 17:16:48 GMT</pubDate>
            <atom:updated>2020-06-28T16:20:21.309Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Web Application Security Assessment using Burp Community Edition | Part — 2| Audit Guidelines | High Impact Web Vulnerability</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*B41EfqdZiQWb3Hf59a2wzQ.jpeg" /></figure><p>The blog [Part-2] basically covers how to check the web application vulnerability with Burp Community Edition. This blog will be very helpful while performing the web application security assessment( VAPT) manually. In this part of the blog, we will cover a few vulnerabilities with High impact severity. So here is the blog.</p><h4><strong>What is X-Forwarded-For and why it is used?</strong></h4><p>The X-Forwarded-For (XFF) header is a header for identifying the originating IP address of a client connecting to a web server through an HTTP proxy or a load balancer. When traffic is intercepted between clients and servers, server access logs contain the IP address of the proxy or load balancer only. To see the original IP address of the client, the X-Forwarded-For request header is used.</p><h3>IP Spoofing (Bypass Whitelisting)</h3><h4>Audit Guideline</h4><ol><li>Try to access the application from any network except the whitelisted one.</li><li>Capture the base request in the burp community and send the request to the repeater.</li><li>Add <strong>X-Forwarded-For </strong>Header in the request and the IP that has whitelisted for application access as Header value. (note- can also check for 0.0.0.0, localhost or 127.0.0.1 if the whitelisted IP is not known.)</li><li>Observe the application will response normally. Hence,bypassed the whitelisting to access the application.</li></ol><p><strong>Proof of Concept</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a11anrDF95uWUJ2f1FrUmg.png" /><figcaption>Request without X-Forwarded-For Header</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*68Kw0K7d1RdqLqdmBQ6diQ.png" /><figcaption>Request with X-Forwarded-For Header</figcaption></figure><h4>Reference</h4><p><a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For">https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eace9bcbcb9f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Application Security Assessment using Burp Community Edition | Part — 1 | Audit Guidelines |…]]></title>
            <link>https://rishuranjanofficial.medium.com/web-application-security-assessment-using-burp-community-edition-part-1-audit-guidelines-51f05cf31fb0?source=rss-d981ba3dbc86------2</link>
            <guid isPermaLink="false">https://medium.com/p/51f05cf31fb0</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Rishu Ranjan]]></dc:creator>
            <pubDate>Sun, 17 Nov 2019 17:47:13 GMT</pubDate>
            <atom:updated>2020-07-26T10:24:19.269Z</atom:updated>
            <content:encoded><![CDATA[<h3>Web Application Security Assessment using Burp Community Edition | Part — 1 | Audit Guidelines | High Impact Web Vulnerability</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*LaKnN_yjpu9aCs14MYIXbA.jpeg" /><figcaption>Web Application Security</figcaption></figure><p>The blog basically covers how to check to web application vulnerability with Burp Community Edition. This blog will be very helpful while performing the web application security assessment manually. In this part of the blog, we will cover a few vulnerabilities with High impact severity. So here is the blog.</p><h3>HTTP PUT method is enabled</h3><h4>Audit Guideline</h4><p>1) Capture the base request in the burp community and send the request to the repeater.</p><p>2) Change the request method to PUT and set the path with a file name as /test/shell.php and send the request to the application server.</p><p>3) Observe the response if the server response with <strong>201 Created</strong> response. Then the application is vulnerable.</p><p>4) Now upload the shellcode as shown below and BOOM. Happy RCEing.</p><p>Note- If the PUT method is not allowed on base URL/request trying uploading on a different directory in the application.</p><p><strong>Proof of Concept</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*IuKQIXI9G2hTpIp9A_Q1JA.png" /><figcaption>A web shell is uploaded using the PUT method</figcaption></figure><h3>Out-of-band resource load (HTTP)</h3><h4>Audit Guideline</h4><p>1) Capture the base request in the burp community and send the request to the repeater.</p><p>2) Change the request path to any internal or external URL. For eg. change the request path to <a href="https://www.lucideus.com./">https://www.lucideus.com.</a></p><p>3) From Exhibit below, it can be observed that the application includes the response of <a href="https://www.lucideus.com./">https://www.lucideus.com.</a></p><p><strong>Proof of Concept</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/891/1*Hn1176xYDTGbCHT8gj6KxQ.png" /><figcaption>Application is fetching the pages of another website in response</figcaption></figure><h3>HTTP response header injection</h3><h4>Audit Guideline</h4><p>1)Capture the request in the burp community and send the request to the repeater.</p><p>2) Try Injecting some value For e.g “abcd” in the URL before the parameters start. The injected value will be visible in the X-Cache-Key response header as seen in the Exhibit 3 below.</p><p>3) This can further be exploited to change the Content Type and execute malicious javascript payloads as seen in Exhibit 4 and Exhibit 5, thereby leading to Reflected Cross-Site Scripting.</p><p><strong>Proof of Concept</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*7b605jxnrGszT-LEZFQkiw.png" /><figcaption>Exhibit 3</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/1*angIZ5r_K-sEuyIoyDWoSQ.png" /><figcaption>Exhibit 4</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*nc34AHnbzvPWsjKArJVCMA.png" /><figcaption>Exhibit 5</figcaption></figure><p>Hope you like this blog. The next part is coming soon. Please give your valuable feedback on this blog. You can comment if you want details in-depth on the web vulnerabilities mentioned above or any web-related vulnerability.</p><p><a href="https://blog.lucideus.com/2019/11/find-web-vulnerability-manually.html">https://blog.lucideus.com/2019/11/find-web-vulnerability-manually.html</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51f05cf31fb0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Text Based Injection | Content Spoofing | Low Impact Common Web Vulnerability]]></title>
            <link>https://rishuranjanofficial.medium.com/text-based-injection-content-spoofing-low-impact-common-web-vulnerability-c4b60f43067d?source=rss-d981ba3dbc86------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4b60f43067d</guid>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[vulnerability-management]]></category>
            <dc:creator><![CDATA[Rishu Ranjan]]></dc:creator>
            <pubDate>Wed, 13 Nov 2019 18:36:03 GMT</pubDate>
            <atom:updated>2019-11-14T03:53:16.443Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y81rx-1ncwxLtNi2YXSCkw.png" /><figcaption>Text Based Injection- Content Spoofing</figcaption></figure><p><strong>Text Based Injection:</strong> Text injection or Text-Based Injection(TBI) is an injection in which user input is reflected as it is in the application response as plaintext. This is one of the ways to perform content spoofing also referred to as content injection or virtual defacement which can be used in phishing attacks.</p><p>An application is vulnerable to Text injection when it does not properly handle user-supplied data, an attacker can supply content to a web application, typically via a parameter value, or from the URL only that is reflected back to the user. The user will be presented with a modified page under the context of the trusted domain.</p><p><strong>Attack Type:</strong> Client-Side Vulnerability</p><p><strong>Severity:</strong> Low</p><h4>Audit Guidelines</h4><p>Text injection can be easily found where</p><ol><li>User input via parameter or directly in the URL is reflected in the page response.</li><li>Content-Type: text/plain</li><li>Application is giving default error pages</li></ol><h4>Proof of Concept</h4><p>If you research little more to understand why it is happening and what is the issue here. You will get an answer for ‘what is the issue’ that the application is giving a default error page.</p><p>For ‘why it is happening’, we know the answer, right?</p><p>Anyway, the answer is user input via parameter or directly in the URL is reflected in the page response.</p><p><strong>Error Page</strong></p><p>URL- <a href="https://example.com/captcha">https://example.com/captcha</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zZQJ44OgTLd80IY1WIZ0pQ.png" /><figcaption>Error page</figcaption></figure><p><strong>Modified Error Page</strong></p><p>URL- <a href="https://example.com/captcha/SS%2F%20%20%20is%20not%20available.%20Please%20visit%20-%20-%20-%20-%20https://attacker.com%20%20-%20-%20-%20-%20as%20resource%20">https://example.com/captcha/SS%2F%20%20%20is%20not%20available.%20Please%20visit%20-%20-%20-%20-%20https://attacker.com%20%20-%20-%20-%20-%20as%20resource%20</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jYzsNWlw4T5-_VzwQIe7Zg.png" /><figcaption>Modified Error Page</figcaption></figure><p><strong>How Google Do it</strong></p><p>Google handles the error pages really well. Here is the screenshot for your reference.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DtOp4alR0aEt6TnxFnMk7A.png" /><figcaption>Good Handling of user-supplied input in URL by Google</figcaption></figure><h4>Impact</h4><p>An attacker can use text injection vulnerability to present a customized message on the application that can phish users into believing that the message is legitimate. The intent is typical to tick victims, although sometimes the actual purpose may be to simply misrepresent the organization or an individual. This attack is typically used as, or in conjunction with, social engineering because the attack is exploiting a code-based vulnerability and a user’s trust. As a side note, this attack is widely misunderstood as a kind of a bug that brings no impact.</p><h4>Recommendations</h4><p>The application should only accept the values and types that are defined for parameters and should be checked at the server-side whether there is change content, if there is change, then the application should reject that request. Also, never construct and send messages via URL in the page response. Prefer using messages predefined in a property file.</p><p>For Default Error pages</p><p>The application configuration should specify a default error page in order to guarantee that the application will never leak error messages to an attacker. Handling standard HTTP error codes is user-friendly in addition to being a good security practice, and can be done by specifying custom error pages for error codes like 404, 403, 500, etc.</p><h4>References</h4><p><a href="https://www.owasp.org/index.php/Content_Spoofing">https://www.owasp.org/index.php/Content_Spoofing</a></p><p><a href="https://resources.infosecinstitute.com/content-spoofing/#gref">https://resources.infosecinstitute.com/content-spoofing/#gref</a></p><p><a href="https://www.geeksforgeeks.org/content-spoofing/">https://www.geeksforgeeks.org/content-spoofing/</a></p><p><a href="https://www.digitalocean.com/community/tutorials/how-to-configure-apache-to-use-custom-error-pages-on-ubuntu-14-04">https://www.digitalocean.com/community/tutorials/how-to-configure-apache-to-use-custom-error-pages-on-ubuntu-14-04</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4b60f43067d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microsoft Bot Framework — Unvalidated File Upload | Online Service Acknowledgements]]></title>
            <link>https://rishuranjanofficial.medium.com/microsoft-bot-framework-unvalidated-file-upload-online-service-acknowledgements-abc2fea2eb8f?source=rss-d981ba3dbc86------2</link>
            <guid isPermaLink="false">https://medium.com/p/abc2fea2eb8f</guid>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[microsoft]]></category>
            <dc:creator><![CDATA[Rishu Ranjan]]></dc:creator>
            <pubDate>Tue, 15 Oct 2019 16:50:36 GMT</pubDate>
            <atom:updated>2019-10-15T16:50:36.962Z</atom:updated>
            <content:encoded><![CDATA[<h3>Microsoft Bot Framework — Unvalidated File Upload | Online Service Acknowledgements</h3><p><strong>Microsoft Bot Unvalidated File Upload:</strong> The security issue allows a malicious actor to upload any file without validating the extension or content type of the file.</p><p><strong>Acknowledgment</strong>: Microsoft Online Service Acknowledgements for July 2019 (<a href="https://portal.msrc.microsoft.com/en-us/security-guidance/researcher-acknowledgments-online-services?rtc=1">https://portal.msrc.microsoft.com/en-us/security-guidance/researcher-acknowledgments-online-services?rtc=1</a>)</p><p><strong>About Microsoft Bot Framework: </strong>Azure Bot Service enables you to build intelligent, enterprise-grade bots with ownership and control of your data. Begin with a simple Q&amp;A bot or build a sophisticated virtual assistant.</p><p>Use comprehensive open source SDK and tools to easily connect your bot to popular channels and devices. Give your bot the ability to speak, listen, and understand your users with native integration to Azure Cognitive Services.</p><p><strong>URL</strong></p><p><a href="https://webchat.botframework.com/embed/TaxiLimeBot?s=xMHlV-9UR7c.cwA._H8.kLpVmFx6sOsqfBAKTic2_YqvcPsy5N8XBXT5a4h4jio">https://webchat.botframework.com/embed/TaxiLimeBot?s=xMHlV-9UR7c.cwA._H8.kLpVmFx6sOsqfBAKTic2_YqvcPsy5N8XBXT5a4h4jio</a></p><p><a href="https://webchat.botframework.com/embed/SPAdminBotBeta?s=onFqEMZTaC4.cwA.Cwo.jTm_RSmb0Svg-areEJIwczJ3zwnFF1Bj64ccYtJEcT4">https://webchat.botframework.com/embed/SPAdminBotBeta?s=onFqEMZTaC4.cwA.Cwo.jTm_RSmb0Svg-areEJIwczJ3zwnFF1Bj64ccYtJEcT4</a></p><p><a href="https://webchat.botframework.com/embed/hipstercatbot?s=dNn17GME34k.cwA.Q2M.PngrX97_gN0-KZIvTUYnfqDTIYA6SjuaAt4qvIiSnGM">https://webchat.botframework.com/embed/hipstercatbot?s=dNn17GME34k.cwA.Q2M.PngrX97_gN0-KZIvTUYnfqDTIYA6SjuaAt4qvIiSnGM</a></p><p><strong><em>[Note- All webchat bots are Vulnerable]</em></strong></p><p><strong>Impact</strong></p><ul><li><strong>Client-side attacks: </strong>Uploading malicious files can make the website vulnerable to client-side attacks such as XSS or HTML Injection, etc which can redirect users to a phishing website.</li><li><strong>Trust Breach:</strong> The attacker can use the upload functionality to upload malware which he/she can use to store or transmit to the victim for malware attack. The trust of the user on Microsoft is impacted as the malware is transmitted via Microsoft related domain.</li></ul><p><strong>Steps to Reproduce</strong></p><p><strong>Instance 1: Client-side attacks-Reflected XSS</strong></p><p>Severity: High</p><p>CVSS Score: <strong>7.1</strong></p><p>CVSS Vector: AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N/E:H/RL:O/RC:C/CR:X/IR:M/AR:X/MAV:X/MAC:X/MPR:X/MUI:X/MS:X/MC:X/MI:X/MA:X</p><p><strong>Proof of Concept:</strong></p><p>Step 1: Create a SVG(Scalable Vector Graphics) file with malicious javascript as shown below in Exhibit-1.1.1.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1Df5V01XU2sdHuoD" /><figcaption>Exhibit-1.1.1</figcaption></figure><p>Step 2: Navigate to <a href="https://webchat.botframework.com/embed/TaxiLimeBot?s=xMHlV-9UR7c.cwA._H8.kLpVmFx6sOsqfBAKTic2_YqvcPsy5N8XBXT5a4h4jio">https://webchat.botframework.com/embed/TaxiLimeBot?s=xMHlV-9UR7c.cwA._H8.kLpVmFx6sOsqfBAKTic2_YqvcPsy5N8XBXT5a4h4jio</a></p><p>Step 3: Upload the created ‘kiwi.svg’ on the webchat. Observe that the file is uploaded successfully.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QGiyU64OMdpejspJ" /><figcaption>Exhibit-1.1.2</figcaption></figure><p>Step 4: Click on the uploaded file to get the link of the attachment</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*R66W2OPrzRN90T60" /><figcaption>Exhibit-1.1.3</figcaption></figure><p>Step 5: Open the link in another browser(Here- Google chrome) and observe that the browser will give the pop up. The link can be shared/used to trick users to redirect to some phishing pages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FvMlUoKhw8gJTVVW" /><figcaption>Exhibit-1.1.4</figcaption></figure><p><strong>Expected Result:</strong></p><p>The bot frame should not allow or block the harmful extensions like svg file to be uploaded.</p><p><strong>Observed Result:</strong></p><p>The attacker has uploaded the svg file and the link can be shared/used to trick users to redirect to some phishing pages.</p><p><strong>Instance 1: Client-side attacks-HTML Injection</strong></p><p>Severity: Medium</p><p>CVSS Score: <strong>4.1</strong></p><p>CVSS Vector: AV:P/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N/E:H/RL:O/RC:C/CR:X/IR:M/AR:X/MAV:X/MAC:X/MPR:X/MUI:X/MS:X/MC:X/MI:X/MA:X</p><p><strong>Proof of Concept:</strong></p><p>Step 1: Start server(Here- ngrok used) to get a public domain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/0*KbA7jOCjAaYwI7pa" /><figcaption>Exhibit-1.2.1</figcaption></figure><p>Step 2: Create a HTML form which is submitting the form data to the above server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*j5RMv93U32Nr3uGK" /><figcaption>Exhibit-1.2.2</figcaption></figure><p>Step 3: Navigate to the <a href="https://webchat.botframework.com/embed/SPAdminBotBeta?s=onFqEMZTaC4.cwA.Cwo.jTm_RSmb0Svg-areEJIwczJ3zwnFF1Bj64ccYtJEcT4">https://webchat.botframework.com/embed/SPAdminBotBeta?s=onFqEMZTaC4.cwA.Cwo.jTm_RSmb0Svg-areEJIwczJ3zwnFF1Bj64ccYtJEcT4</a></p><p>Step 4: Upload the created ‘Microsoft SSO.html’ on the webchat. Observe that the file is uploaded successfully.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*A-Gu1MPwMv6tj_nB" /><figcaption>Exhibit-1.2.3</figcaption></figure><p>Step 4: Click on the uploaded file to get the link of the attachment and open in the browser. Enter the credentials and submit the form.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SEtIeovhjM_GF5WN" /><figcaption>Exhibit-1.2.4</figcaption></figure><p>Step 5: Observe that the user credentials are logged on my server. The link of the form can be shared/used to trick user to get his/her Microsoft login credentials. The user will submit credentials considering it as Microsoft related domain and hence genuine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MQuFSufQkn723tg1" /><figcaption>Exhibit-1.2.5</figcaption></figure><p><strong>Expected Result:</strong></p><p>The bot frame should not allow or block the harmful extensions like html file to be uploaded.</p><p><strong>Observed Result:</strong></p><p>The attacker has uploaded the html file which can be accessed only locally and the link can be used to trick users to redirect to some phishing pages.</p><p><strong>Instance 2: Trust Breach- Mode for Malware Transmission</strong></p><p>Severity: Low</p><p>CVSS Score:<strong> 3.8</strong></p><p>CVSS Vector: AV:P/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N/E:U/RL:O/RC:C/CR:X/IR:M/AR:X/MAV:X/MAC:X/MPR:X/MUI:X/MS:X/MC:X/MI:X/MA:X</p><p><strong>Proof of Concept:</strong></p><p>Step 1: Navigate to the <a href="https://webchat.botframework.com/embed/SPAdminBotBeta?s=onFqEMZTaC4.cwA.Cwo.jTm_RSmb0Svg-areEJIwczJ3zwnFF1Bj64ccYtJEcT4">https://webchat.botframework.com/embed/hipstercatbot?s=dNn17GME34k.cwA.Q2M.PngrX97_gN0-KZIvTUYnfqDTIYA6SjuaAt4qvIiSnGM</a></p><p>Step 2: Upload the Test_Malware.exe and observe that the file is uploaded successfully. The uploaded file is having a link now which can be shared/used for malware attack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*-k-73pXGy0loBkRPfj1F9Q.png" /><figcaption>Exhibit-2.1</figcaption></figure><p><strong>Expected Result:</strong></p><p>The bot frame should not allow or block the harmful extensions like exe file to be uploaded.</p><p><strong>Observed Result:</strong></p><p>The attacker has uploaded the exe file which can be accessed locally and the link can be used to trick users to perform malicious activity.</p><p><strong>Note- </strong>HTML Injection and Mode for Malware Transmission are possible only when attacker has the physical access of the user. The impact of both is very less, but it is an issue. These points should also be considered for patch subject to priority of Microsoft.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abc2fea2eb8f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>