<?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 George Torres on Medium]]></title>
        <description><![CDATA[Stories by George Torres on Medium]]></description>
        <link>https://medium.com/@georgeppmc?source=rss-d8ca5b09be6c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*croM7cCCDFA4uE-j</url>
            <title>Stories by George Torres on Medium</title>
            <link>https://medium.com/@georgeppmc?source=rss-d8ca5b09be6c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:40:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@georgeppmc/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[403 Forbidden Bypass Exposing API Key]]></title>
            <link>https://medium.com/@georgeppmc/403-forbidden-bypass-exposing-api-key-b5c9df9daeb3?source=rss-d8ca5b09be6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5c9df9daeb3</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[George Torres]]></dc:creator>
            <pubDate>Thu, 21 Mar 2024 21:05:49 GMT</pubDate>
            <atom:updated>2024-03-21T21:07:03.341Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/785/1*cw9AjvYNgk7bHcwuSJnE_g.png" /></figure><ol><li><strong>Introduction</strong></li></ol><p>This report outlines the discovery and exploitation of a vulnerability on <em>redacted.com</em>. I have to keep the company name private due to a NDA. The vulnerability allowed for a bypass of the 403 Forbidden status code, granting access to a secret API key. This report aims to provide a detailed account of the findings and the subsequent steps taken.</p><p>2. <strong>Background</strong></p><p>While conducting a thorough analysis of the redacted website’s functionalities with Burp Suite, I decided to investigate the potential presence of a path traversal vulnerability.</p><blockquote>Path traversal, also known as directory traversal, is an attack technique that seeks to access files and directories located outside the web root folder. By manipulating variables referencing files using specific character sequences, such as “../” or absolute file paths, an attacker may gain unauthorized access to sensitive files, including application source code, configuration files, or even critical system files. — OWASP</blockquote><p>3. <strong>Discovery</strong></p><p>Although I was unable to identify a path traversal vulnerability during the analysis, I discovered an interesting endpoint, “/API/V2/,” within the website’s structure. Intrigued by the possibility of uncovering potential vulnerabilities, I attempted to access the endpoint by removing the “/v2/” segment from the URL. Surprisingly, this action redirected them to a page containing API documentation for a third-party service.</p><p>4. <strong>Initial Access</strong></p><p>Denied Upon accessing the API documentation page, I received a 403 Forbidden status code, indicating restricted access. Undeterred, I continued my exploration and experimentation to determine if any security weaknesses could be exploited.</p><p>5. <strong>403 Forbidden Bypass</strong></p><p>During their investigation, I decided to try URL encoding the endpoint. This technique involves encoding special characters in a URL to ensure proper transmission and interpretation by web servers. By applying URL encoding to the endpoint, I discovered that the 403 Forbidden page could be bypassed successfully, granting access to the previously restricted API documentation.</p><p>6. <strong>Exposure of Secret API Key</strong></p><blockquote>What is an API Key? An application programming interface (API) key is a code used to identify and authenticate an application or user. They control requests made between programs, how those requests are made, and the data formats used.</blockquote><p>Once the 403 Forbidden bypass was accomplished, I noticed that the response in burp contained a secret API key. This key, originally intended to remain concealed, was inadvertently exposed due to the vulnerability. It is important to note that I acted responsibly and did not misuse or disclose this information to any unauthorized parties.</p><p>7. <strong>Responsible Disclosure</strong></p><p>I reported their findings to the redacted website’s security team on Hacker0ne, providing a detailed account of the vulnerability, the steps to reproduce it, and the potential risks associated with the exposed API key. The company acknowledged the report as informative, but did not issue a bounty for the discovery. :(((</p><p>8. <strong>Conclusion</strong></p><p>While the company did not recognize my findings with a bounty, the successful bypass of the 403 Forbidden status code represents a significant achievement in my bug bounty hunting journey. The discovery of this vulnerability and the subsequent responsible disclosure process not only contributed to my personal growth but also highlighted the importance of thorough security testing and continuous improvement in web application development. I express gratitude to all who have read this report and hopes that it serves as an educational resource for others interested in Bug Bounty Hunting.</p><p>Another thing, I’m always willing to collaborate with other researchers! Feel free to reach out to me!</p><p>Happy hacking!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5c9df9daeb3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unveiling the Dangers of CWE-319: Clear Text Transmission of Sensitive Information]]></title>
            <link>https://medium.com/@georgeppmc/unveiling-the-dangers-of-cwe-319-clear-text-transmission-of-sensitive-information-1ada2d1f4ca5?source=rss-d8ca5b09be6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ada2d1f4ca5</guid>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[George Torres]]></dc:creator>
            <pubDate>Sat, 06 Jan 2024 01:57:19 GMT</pubDate>
            <atom:updated>2024-01-06T02:09:57.631Z</atom:updated>
            <content:encoded><![CDATA[<p>Bug bounty programs have become an invaluable resource for organizations to identify and address vulnerabilities in their systems. In my quest as a bug bounty hunter, I recently encountered a vulnerability known as CWE-319: Clear Text Transmission of Sensitive Information.( some developers don’t think its much of an issue.) This blog post aims to shed light on the dangers associated with this vulnerability and how attackers can exploit it to carry out attacks on unsecured networks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*YblMeCMWAltMtbZU6vdNhg@2x.jpeg" /></figure><p>In the picture you can see an arrow pointing to the cleartext password. I have redacted a lot of information due to a non disclosure agreement.</p><p>Understanding CWE-319:</p><p>CWE-319 refers to the transmission of sensitive information, such as passwords, credit card numbers, or any other confidential data, over unencrypted channels. When data is transmitted in clear text, it becomes susceptible to interception by malicious actors who can exploit this vulnerability to gain unauthorized access to sensitive information.</p><p>The Danger of Clear Text Transmission:</p><p>Clear text transmission of sensitive information poses significant risks to both users and organizations. Let’s dive (he’s a diver) into some of the potential consequences:</p><p>1.</p><p>Man-in-the-Middle Attacks: Attackers can intercept unencrypted network traffic, positioning themselves between the client and the server. By doing so, they can eavesdrop on the communication and capture sensitive information, including passwords, banking details, or personal information. This information can then be exploited for identity theft, financial fraud, or other malicious activities.</p><p>2.</p><p>Data Breaches and Privacy Violations: Clear text transmission exposes sensitive data to unauthorized individuals who can exploit it for personal gain. This can lead to data breaches, compromising users’ privacy, damaging the reputation of the affected organization, and resulting in legal consequences.</p><p>3.</p><p>Credential Stuffing and Account Takeovers: When passwords are transmitted in clear text, attackers can intercept them and use them to gain unauthorized access to user accounts. This can lead to account takeovers, allowing attackers to manipulate or misuse the compromised accounts for their own purposes.</p><p>Preventing Clear Text Transmission Vulnerabilities:</p><p>To mitigate the risks associated with CWE-319, organizations should implement the following measures:</p><p>Encryption: Ensure that sensitive data is transmitted over secure channels using encryption protocols such as HTTPS, SSL/TLS, or other industry-standard encryption mechanisms. This ensures that data remains confidential during transmission and cannot be easily intercepted.</p><p>2.</p><p>Secure Communication Practices: Implement secure coding practices that include proper handling and storage of sensitive data. Employ secure communication libraries and frameworks that automatically encrypt and protect data in transit.</p><p>3.</p><p>Regular Security Audits: Conduct periodic security audits and vulnerability assessments to identify and remediate any clear text transmission vulnerabilities. This will help ensure that sensitive data is adequately protected.</p><p>Conclusion:</p><p>Although my recent submission for a bug bounty program turned out to be a duplicate (meaning another hacker found and reported the vulnerability before I did) the company still thanked me for my submission and the experience taught me valuable lessons about the dangers associated with CWE-319: Clear Text Transmission of Sensitive information</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/585/1*NDy_tEQdg323y0dwVHSuew@2x.jpeg" /></figure><p>Until next time🤙</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ada2d1f4ca5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My First Bug Bounty: Lessons Learned and Money Earned]]></title>
            <link>https://medium.com/@georgeppmc/my-first-bug-bounty-lessons-learned-and-money-earned-d6fc31744621?source=rss-d8ca5b09be6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6fc31744621</guid>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[bug-hunting]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[hackerone]]></category>
            <dc:creator><![CDATA[George Torres]]></dc:creator>
            <pubDate>Wed, 03 Jan 2024 18:30:23 GMT</pubDate>
            <atom:updated>2024-01-03T18:40:32.539Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey everyone! Im excited to share my first bug bounty experience with you. It all started when I was bored and began a security test on a buy now/pay later application from a prominent company. When testing this company, I stumbled upon an open redirect</p><p>“An open redirect vulnerability occurs when an application allows a user to control a redirect or forward to another URL. If the app does not validate untrusted user input, an attacker could supply a URL that redirects an unsuspecting victim from a legitimate domain to an attacker’s phishing site.”</p><p>Open Redirects may seem harmless, but they can be dangerous and can really harm the end users.</p><p>How it happened: There was redirect parameter in the URL and it caught my attention. I decided to put it to the test. I replaced the redirect url with Twitter.com and BAM! A open redirect. I was so happy i actually couldnt believe it. “No way this company is vulnerable to a open redirect” I thought to myself. But to my surprise, I had successfully got the application to send me to my desired endpoint.</p><p>Realizing the impact of this vulnerability, I understood how an attacker could exploit it. By manipulating the redirect parameter, they could craft convincing phishing attacks, tricking users into visiting malicious websites while thinking they were accessing a trusted source.</p><p>With my findings in hand, I promptly created a detailed report and submitted it to the company on Hackerone. The wait for their response felt like an eternity, but eventually, they triaged the report. Their validation of the vulnerability was a validation of my skills and instincts.</p><p>In the end, I received a $150 bounty for my contribution. More importantly, I gained invaluable knowledge and experience, understanding the importance of trusting my instincts and thoroughly testing every aspect of a system.</p><p>This bug bounty journey has taught me that even seemingly insignificant vulnerabilities can have significant consequences. It’s a reminder to stay curious, explore, and report responsibly. Trust your instincts, test everything, and who knows, you might uncover something truly impactful. Stay tuned for more bug bounty adventures.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6fc31744621" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>