<?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 Gökhan Güzelkokar on Medium]]></title>
        <description><![CDATA[Stories by Gökhan Güzelkokar on Medium]]></description>
        <link>https://medium.com/@gkhck496?source=rss-8354dfe8fea1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*VO9Jl01UtyKWHKmkvn4k2Q.jpeg</url>
            <title>Stories by Gökhan Güzelkokar on Medium</title>
            <link>https://medium.com/@gkhck496?source=rss-8354dfe8fea1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:51:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gkhck496/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[Multi-Tenant Authorization Bypass via Host Header Manipulation]]></title>
            <link>https://medium.com/@gkhck496/multi-tenant-authorization-bypass-via-host-header-manipulation-53e350b11468?source=rss-8354dfe8fea1------2</link>
            <guid isPermaLink="false">https://medium.com/p/53e350b11468</guid>
            <dc:creator><![CDATA[Gökhan Güzelkokar]]></dc:creator>
            <pubDate>Sat, 07 Feb 2026 12:56:56 GMT</pubDate>
            <atom:updated>2026-02-07T12:56:56.864Z</atom:updated>
            <content:encoded><![CDATA[<p>While testing a private bug bounty program, I encountered an IDOR vulnerability. At first glance, it appeared to be a simple IDOR where I could manipulate the id parameter and write data to another user&#39;s record. However, there was an unusual behavior in how the system handled subdomains.</p><p>Each user has a dedicated subdomain:</p><ul><li>user1.domain.com → userId = 1234</li><li>user2.domain.com → userId = 4321</li></ul><p>There is an endpoint that allows users to add passport information. This action can only be performed once after submission, the data cannot be modified.</p><p>Example request:</p><pre>POST /api/v3/passport/addPassport<br>Host: user1.domain.com<br>Authorization: &lt;user1&#39;s sessionId&gt;<br><br>id=1234&amp;passportNo=00000000000&amp;name=Test&amp;address=Test+test+test+5<br><br>201 Created</pre><p>The stored data can then be retrieved using:</p><pre>GET /api/v3/passport?userId=1234<br>Host: user1.domain.com<br>Authorization: &lt;user1&#39;s sessionId&gt;<br><br><br>200 OK<br><br>{data}</pre><p>To test for IDOR, I modified the id parameter and changed it from 1234 to 4321:</p><pre>POST /api/v3/passport/addPassport<br>Host: user1.domain.com<br>Authorization: &lt;user1&#39;s sessionId&gt;<br><br>id=4321&amp;passportNo=00000000000&amp;name=Test&amp;address=Test+test+test+5<br><br>201 Created</pre><p>The request was accepted and returned 200 OK, indicating that the passport information for userId=4321 was successfully created.</p><p>When retrieving the data from the same subdomain:</p><pre>GET /api/v3/passport?userId=4321<br>Host: user1.domain.com<br>Authorization: &lt;user1&#39;s sessionId&gt;<br><br>200 OK<br><br>{data}</pre><p>There is an issue here: although the request was successfully processed with another userId, it didn’t affect user2’s requests. The data seems to be stored only under the same subdomain where the request was made.</p><pre>GET /api/v3/passport?userId=4321<br>Host: user2.domain.com<br>Authorization: &lt;user2&#39;s sessionId&gt;<br><br><br>404 NOT FOUND</pre><p>This is an IDOR vulnerability with limited impact. To demonstrate a real security impact, I would need to escalate it and be able to write this data to another user’s subdomain.</p><p>Now I’ll explain what I tried and it worked successfully. This turned out to be a major misconfiguration. I honestly couldn’t believe it worked.</p><p>The only thing I did was change the Host header to user2’s domain. That was it. Using user1’s session, I was able to post data to user2’s subdomain. At first, I genuinely couldn’t believe it worked I initially thought it might be related to kind of caching mechanism.</p><pre>POST /api/v3/passport/addPassport<br>Host: user2.domain.com<br>Authorization: &lt;user1&#39;s sessionId&gt;<br><br>id=4321&amp;passportNo=00000000000&amp;name=Test&amp;address=Test+test+test+5<br><br>201 Created</pre><pre>GET /api/v3/passport?userId=4321<br>Host: user2.domain.com<br>Authorization: &lt;user2&#39;s sessionId&gt;<br><br>200 OK</pre><p>Bingo! If I can modify the Host header and successfully send this request, it means the same approach works across all API endpoints. This represents a critical vulnerability for the company.</p><pre>GET /api/v3/passport?userId=4321<br>Host: user2.domain.com<br>Authorization: &lt;user1&#39;s sessionId&gt;!!!<br><br>200 OK</pre><p>This vulnerability allows unrestricted access to all API endpoints across every subdomain, exposing more than 50 endpoints, including those that handle critical PII.</p><p><strong><em>The company has a strong security posture; however, after changes to their API architecture, a minor misconfiguration resulted in this vulnerability.</em></strong></p><h4>Timeline</h4><p>Reported <br><strong>January 8, 2026, 5:17pm UTC</strong></p><p>Rewarded with <strong>$$$$</strong> bounty<br><strong>January 8, 2026, 8pm UTC</strong></p><p>Resolved<br><strong>January 8, 2026, 9:34pm UTC</strong></p><p>Thank you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53e350b11468" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[S3 Bucket Takeover: Discovering a Bucket Inside a Bucket for $1000]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@gkhck496/s3-bucket-takeover-discovering-a-bucket-inside-a-bucket-for-1000-8506f4ec07a4?source=rss-8354dfe8fea1------2"><img src="https://cdn-images-1.medium.com/max/800/1*YeJ6FlyJaI-Hj_9RrlWiaQ.png" width="800"></a></p><p class="medium-feed-snippet">In this article, I will write about a security vulnerability I found in a private program associated with the HackerOne platform and&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@gkhck496/s3-bucket-takeover-discovering-a-bucket-inside-a-bucket-for-1000-8506f4ec07a4?source=rss-8354dfe8fea1------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@gkhck496/s3-bucket-takeover-discovering-a-bucket-inside-a-bucket-for-1000-8506f4ec07a4?source=rss-8354dfe8fea1------2</link>
            <guid isPermaLink="false">https://medium.com/p/8506f4ec07a4</guid>
            <dc:creator><![CDATA[Gökhan Güzelkokar]]></dc:creator>
            <pubDate>Thu, 05 Dec 2024 11:03:38 GMT</pubDate>
            <atom:updated>2024-12-05T11:03:38.871Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[From Wayback Machine to AWS Metadata: Uncovering SSRF in a Production System Within 5 Minutes]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@gkhck496/from-wayback-machine-to-aws-metadata-uncovering-ssrf-in-a-production-system-within-5-minutes-2d592875c9ab?source=rss-8354dfe8fea1------2"><img src="https://cdn-images-1.medium.com/max/2600/1*K-wgSrqAbG6Bhfhw8sNJGw.png" width="3390"></a></p><p class="medium-feed-snippet">Oh my waybackmachine! It&#x2019;s really great tool to get hidden urls. You can use some tools to get urls like gau and waybackurls, but in this&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@gkhck496/from-wayback-machine-to-aws-metadata-uncovering-ssrf-in-a-production-system-within-5-minutes-2d592875c9ab?source=rss-8354dfe8fea1------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@gkhck496/from-wayback-machine-to-aws-metadata-uncovering-ssrf-in-a-production-system-within-5-minutes-2d592875c9ab?source=rss-8354dfe8fea1------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d592875c9ab</guid>
            <dc:creator><![CDATA[Gökhan Güzelkokar]]></dc:creator>
            <pubDate>Wed, 27 Nov 2024 08:13:03 GMT</pubDate>
            <atom:updated>2024-11-27T08:13:03.976Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[From Long-Term Hacking to Instant Rewards: Finding SQLi in 3 Minutes Worth $3125]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@gkhck496/from-long-term-hacking-to-instant-rewards-finding-sqli-in-3-minutes-worth-3125-ac36c6e950bf?source=rss-8354dfe8fea1------2"><img src="https://cdn-images-1.medium.com/max/1920/1*5aArKuhfBMdJOY196RX6Kw.png" width="1920"></a></p><p class="medium-feed-snippet">I believe that if you want to succeed in bug bounty, you should focus on programs that you have been hacking for a long time, like 2&#x2013;3&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@gkhck496/from-long-term-hacking-to-instant-rewards-finding-sqli-in-3-minutes-worth-3125-ac36c6e950bf?source=rss-8354dfe8fea1------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@gkhck496/from-long-term-hacking-to-instant-rewards-finding-sqli-in-3-minutes-worth-3125-ac36c6e950bf?source=rss-8354dfe8fea1------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac36c6e950bf</guid>
            <category><![CDATA[sql]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[hackerone]]></category>
            <category><![CDATA[sql-injection]]></category>
            <dc:creator><![CDATA[Gökhan Güzelkokar]]></dc:creator>
            <pubDate>Sat, 06 Jul 2024 14:02:24 GMT</pubDate>
            <atom:updated>2024-07-06T17:18:55.612Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Introduction to Burpsuite Bambdas Feature]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@gkhck496/introduction-to-burpsuite-bambda-feature-4c6b5fbc168d?source=rss-8354dfe8fea1------2"><img src="https://cdn-images-1.medium.com/max/1422/1*r-zsE5bIbTG3rjGaiuBQ5A.png" width="1422"></a></p><p class="medium-feed-snippet">Burp suite brought a very nice feature to the filtering section. Meet Bambda. Bambda allows to write Java based filter for your http&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@gkhck496/introduction-to-burpsuite-bambda-feature-4c6b5fbc168d?source=rss-8354dfe8fea1------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@gkhck496/introduction-to-burpsuite-bambda-feature-4c6b5fbc168d?source=rss-8354dfe8fea1------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c6b5fbc168d</guid>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[burpsuite]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Gökhan Güzelkokar]]></dc:creator>
            <pubDate>Sat, 09 Dec 2023 15:32:45 GMT</pubDate>
            <atom:updated>2023-12-09T20:31:21.070Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Hacking For 20 Hours in a Private Bug Bounty Program]]></title>
            <link>https://medium.com/@gkhck496/hacking-for-20-hours-in-a-private-bug-bounty-program-c466193cb69a?source=rss-8354dfe8fea1------2</link>
            <guid isPermaLink="false">https://medium.com/p/c466193cb69a</guid>
            <category><![CDATA[hackerone]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Gökhan Güzelkokar]]></dc:creator>
            <pubDate>Tue, 22 Aug 2023 21:56:09 GMT</pubDate>
            <atom:updated>2023-08-23T08:20:28.850Z</atom:updated>
            <content:encoded><![CDATA[<p>I decided to hack on private program for 20 hours, In this story, I’ll share my experiences about my journey.</p><p>The most common mistake in Bug bounty, when bug hunter picked a target to hack, hacker doesn’t spend a long time on the target. So, when you pick a target hack on it for a long time. Actually, 20 hours is not a long time but it’s enough to understand company logic. Let’s talk about steps.</p><h3>1 — Use timer</h3><p>When you start to hack focus and use timer. I used <a href="https://app.clockify.me/">Clockify</a> for this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c8mlAqpAbqKHh9dOJRk3Vw.png" /></figure><h3>2— Take notes</h3><p>Write everything you see about your target, technologies, responses for specific payloads, roles, capabilities for every single role… I will share my template and some example notes for this journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/510/1*9wDNmamVaq3DnZ125jfjjA.png" /><figcaption>Priveleges in your target</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/930/1*XtUjLYCYXlOK_Jl1bAVTQg.png" /><figcaption>Feature of endpoints and your notes about app</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/1*rea1LQeA2YcpnsY3uhFA6A.png" /><figcaption>Error messages</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*FSL-bFZ0M0W9s6rB8uWP9Q.png" /><figcaption>Bugs &amp; Potential Bugs</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/416/1*B0sLm6rISIY4SnyAi7YucA.png" /><figcaption>Reports</figcaption></figure><p>I made 5000$ in this journey. First of all, when I work with timer and notes like this, I enjoyed a lot than classic method. I’ll share some of my reports too. Thanks <a href="https://twitter.com/gregxsunday">gregxsunday</a> for inspiring me!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*drgLcrd4rPN-_fRask3Spw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UdAdcgxo9Hmlt1bthvCepw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*U3x4xspMXDSVmiZvsz1kYw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*DlYR3KdhL2tNvUPCBZ3xtQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*vYdNnH51d1TKQCtkqYrUOA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*Yce56okb7z8FoO00y1MxXg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*qajaPyFertANsNkoIGHS3A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*fFDmkem-pAB317ohvMHKRw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*gEeJhsQbPrOoNgne7alhgw.png" /></figure><p>Thanks you, have a great day.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c466193cb69a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Attacking Misconfigure Spring Boot Actuators]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@gkhck496/attacking-misconfigure-spring-boot-actuators-962a0cf8fcbe?source=rss-8354dfe8fea1------2"><img src="https://cdn-images-1.medium.com/max/1047/1*tEBruLfubD4pee2KCt8pig.png" width="1047"></a></p><p class="medium-feed-snippet">In this story I&#x2019;ll write about spring boot actuators. I&#x2019;ll explain the components and we will see Hackerone reports about it. It&#x2019;s very&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@gkhck496/attacking-misconfigure-spring-boot-actuators-962a0cf8fcbe?source=rss-8354dfe8fea1------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@gkhck496/attacking-misconfigure-spring-boot-actuators-962a0cf8fcbe?source=rss-8354dfe8fea1------2</link>
            <guid isPermaLink="false">https://medium.com/p/962a0cf8fcbe</guid>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[spring-boot]]></category>
            <category><![CDATA[appsec]]></category>
            <category><![CDATA[application-security]]></category>
            <dc:creator><![CDATA[Gökhan Güzelkokar]]></dc:creator>
            <pubDate>Mon, 07 Aug 2023 18:44:21 GMT</pubDate>
            <atom:updated>2023-08-07T18:45:29.076Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Server Side Request Forgery in Company with €900M+ Revenue]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@gkhck496/server-side-request-forgery-in-company-with-900m-revenue-5998f32d6af8?source=rss-8354dfe8fea1------2"><img src="https://cdn-images-1.medium.com/max/1096/1*ec0UGkYP3fX-o_ESsiqYeQ.png" width="1096"></a></p><p class="medium-feed-snippet">In 18 July 2022 exactly 1 year ago today, I will write about interesting and sad story in bug bounty because this company almost have 100+&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@gkhck496/server-side-request-forgery-in-company-with-900m-revenue-5998f32d6af8?source=rss-8354dfe8fea1------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@gkhck496/server-side-request-forgery-in-company-with-900m-revenue-5998f32d6af8?source=rss-8354dfe8fea1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5998f32d6af8</guid>
            <category><![CDATA[appsec]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[ssrf]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Gökhan Güzelkokar]]></dc:creator>
            <pubDate>Tue, 18 Jul 2023 20:10:27 GMT</pubDate>
            <atom:updated>2023-07-18T20:10:27.041Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Zero Trust Architecture (ZTA) — Heart of Security]]></title>
            <link>https://medium.com/@gkhck496/zero-trust-architecture-zta-heart-of-security-1e84adbc3984?source=rss-8354dfe8fea1------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e84adbc3984</guid>
            <category><![CDATA[zero-trust]]></category>
            <category><![CDATA[application-security]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[nist]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <dc:creator><![CDATA[Gökhan Güzelkokar]]></dc:creator>
            <pubDate>Sun, 19 Mar 2023 14:45:56 GMT</pubDate>
            <atom:updated>2023-03-19T14:45:56.204Z</atom:updated>
            <content:encoded><![CDATA[<h3>Zero Trust Architecture (ZTA) — Heart of Security</h3><p>Nowadays, Zero Trust is very important topic in Security world. Zero Trust is a security model or architecture based on access control and least privilege rule.</p><p>Internal or external, you shouldn’t trust anyone and you should configure your system with least access for each user. In this article I’ll explain why you shouldn’t trust anyone including yourself. Let the name of our company be <strong>Seccurre</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wc6ybIwgIW14fviYICBFNA.png" /><figcaption><a href="https://www.strongdm.com/zero-trust">https://www.strongdm.com/zero-trust</a></figcaption></figure><p>In the first scenario Bob is a back-end developer in Seccurre company. Bob needs access to a linux virtual machine (10.0.0.6) in your network. He needs this because of he must manage test environment from the server. Don’t see other things this developer absolutely needs access to this machine. Let see big image of this request.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/651/1*xqIrOGOGBTtLNlQxu-lLaQ.png" /></figure><p>Now Bob has access to 10.0.0.6 machine but wait this machine can access other machines right? Now Bob has access to Elastic Search and admin panel which developed internal. Bob has a problem with this company did you know this? Bob’s manager is mobbing him. So, Bob want to damage this company before leave it. You don’t know people, you don’t know who will do what! Or another scenario Bob will deal with a ransomware for access to machine via clicking a mail attachment and Bob get hacked with his own decision with 50000$ of course. Bob may be a really nice person, but that doesn’t mean he’ll have access to everything because there’s always a risk of being hacked. If you want to a hacking scenario in this situation you can generate million of scenario via adding machines in to the network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/751/1*86VsbglnMmh1ng-dISCFIA.png" /></figure><p>Actually I’m pretty sure this structure is bad, maybe even won’t work but my purpose is explain the risk of improper access controls. I’ll end this in one sentence. The rest is up to your imagination. Admin panel in 10.0.0.7 has RCE and sudo version of machine vulnerable with privilege escalation. In this scenario Bob also can be in C-Level position too.</p><blockquote><strong>So, never trust anyone. Zero trust is heart of security!</strong></blockquote><p>In the second scenario, you have big application to manage your virtual machines and containers. This service responsible with security of your containers. So, Bob is a Junior Security Engineer and want to see vulnerabilities of this managed containers but he don’t know anything about how to write rules for machines and other properties etc. And let’s assume that this is a cloud service. Think about you have more than 200 access role and you can create custom roles. Bob should get Vulnerability Viewer role. He is part of security team but our architecture built on <strong>“Zero Trust”. </strong>Bob could also be an employee of an external company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/1*3ohLgUN9rWVxbmm8qlOCUQ.png" /></figure><p>In this scenario Bob can shutdown all machine willingly or unwillingly doesn’t matter. Bob has GIT and GIT vulnerable with RCE, Bob can be hacked. Bob can leak own credentials anywhere.</p><blockquote><strong>So never trust anyone. Zero trust is heart of security!</strong></blockquote><p>Andre is a linux machine in this company. Maybe no one has access here now, but it doesn’t mean there never will be. So each port and access control very important for every single machine too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*-uNRxOIjIxTqfOnXnztNnA.png" /></figure><p><strong>Zero Trust for Cloud Networking</strong></p><p>To implement a zero trust architecture in a cloud network, the following must be done.</p><ul><li>No inherent trust, so assume local network is hostile</li><li>All traffic should be encrypted</li><li>Enforce policies</li><li>Microsegmentation</li></ul><p>More information about ZTA → <a href="https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-207.pdf">https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-207.pdf</a></p><p>Finally, IAM and Zero Trust are with big relationship and very important for securing each asset. Good segmantation for network and never trust anyone or anything. Have a great day.</p><p>Thank you :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e84adbc3984" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Github CodeQL — Güvenlik Açıklarınızı Tespit Edin]]></title>
            <link>https://medium.com/@gkhck496/github-codeql-g%C3%BCvenlik-a%C3%A7%C4%B1klar%C4%B1n%C4%B1z%C4%B1-tespit-edin-624a74d420?source=rss-8354dfe8fea1------2</link>
            <guid isPermaLink="false">https://medium.com/p/624a74d420</guid>
            <category><![CDATA[scanning]]></category>
            <category><![CDATA[bugs]]></category>
            <category><![CDATA[codeql]]></category>
            <category><![CDATA[code-analysis]]></category>
            <category><![CDATA[vulnerability]]></category>
            <dc:creator><![CDATA[Gökhan Güzelkokar]]></dc:creator>
            <pubDate>Sun, 05 Feb 2023 13:13:42 GMT</pubDate>
            <atom:updated>2023-02-05T13:13:42.708Z</atom:updated>
            <content:encoded><![CDATA[<h3>Github CodeQL — Güvenlik Açıklarınızı Tespit Edin</h3><p>Herkese merhaba, bu yazımda sizlere Github’ın CodeQL aracından bahsedip, önce buraya kod yazarak nasıl para kazanabileceğinizi daha sonra projenizi nasıl tarayacağınızı göstereceğim.</p><p>CodeQL kodlarınızı tarayarak güvenlik açıklarınızı bulmanıza yarayan bir açık kaynak kodlu güvenlik aracıdır. Ayrıca sizler de belirlediğiniz bir güvenlik açığını tespit eden kod bloğunu yazabilirsiniz ve sadece bunu yaparak bile büyük paralar kazanabilirsiniz. Github CodeQL için bir bug bounty programı yürütüyor.</p><p><a href="https://hackerone.com/github-security-lab?type=team">GitHub Security Lab - Bug Bounty Program | HackerOne</a></p><p>Önce bir programlama dili seçiyorsunuz daha sonra o programlama dilinde tespit edeceğiniz açığı seçip kodlamaya başlıyorsunuz. Birkaç örnek verecek olursak;</p><p><a href="https://hackerone.com/reports/1602237">GitHub Security Lab disclosed on HackerOne: PYTHON: CWE-079 - Add...</a></p><p>Burada email injection açıklarını bulmak için bir kod yazılmış ve 4500$ gibi bir ödül ödenmiş. Rapordaki issues kısmına gittiğinizde bu çok güzel bir şekilde açıklanmış.</p><blockquote>This query looks for Python applications that are exposed to sending malicous emails containing reflective XSS. Python applications utilize various email libraries to generate emails. If at any time an email is generated in such a way that user input taints the HTML body of the email, then the user can craft malicious emails that render reflective XSS onto the recipient of the email.</blockquote><p>Daha sonra burada attığı pull request’i görebilirsiniz. Burada farklı kütüphaneler için yazılan tespit koduna göz atalım.</p><p><a href="https://github.com/github/codeql/pull/7127">Python: CWE-079 - Add Email injection query by mrthankyou · Pull Request #7127 · github/codeql</a></p><p>Burada ana konu mail gönderirken reflectedXSS olduğu için kodların büyük bir kısmı reflected xss adlı query’e ve mail alanlarına eklenmiş. Kodu ayrıntılı incelediğinizde kilit noktanın body, mail, sender gibi kullanıcı girdilerinin tespit edilip kontrol edildiğini görebilirsiniz.</p><p>Bir başka örneğe bakalım. Bu sefer de Java olsun.</p><ul><li><a href="https://hackerone.com/reports/807440">GitHub Security Lab disclosed on HackerOne: Java (Maven): Actually...</a></li><li><a href="https://github.com/github/codeql/pull/2413/files">Java: Use of HTTP/FTP to download/upload Maven artifacts by JLLeitschuh · Pull Request #2413 · github/codeql</a></li></ul><p>Burada genel olarak maven’dan çekilen bağımlılıkların (dependency) kontrol edildiği ve duruma göre aksiyon alındığını kolaylıkla görebiliriz. Bu kod parçası için ise 4000$ bir ödeme yapılmış.</p><p><a href="https://hackerone.com/reports/807440">GitHub Security Lab disclosed on HackerOne: Java (Maven): Actually...</a></p><p>Buraya kadar genel bir bilgi ve bu projeye nasıl katkıda bulunup para kazanabilirsinizi anlatmış oldu. Diğer bulgu ve ödüllere <a href="https://hackerone.com/github-security-lab/hacktivity?filter=type:public">buradan</a> ulaşabilirsiniz.</p><p>Şimdi de bu güzel aracı kullanmaya çalışalım. Bir projeyi forklayalım.</p><p><a href="https://github.com/gkhan496/vulnerable-spring-boot-application">GitHub - gkhan496/vulnerable-spring-boot-application</a></p><p>Daha sonra burada security sekmesine gelip Code Scanning’e tıklıyoruz.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IDIQh5LVrgEcuyIjTPJNeQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*277u3qvZC9mrMJHZ2loiKQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vimfL0Dqc1o2O-F9zPYLcQ.png" /></figure><p>Burada advance dediğimizde karşımıza<strong> codeql.yml </strong>adında bir konfigürasyon dosyası geliyor. Burada dil ve branch otomatik olarak geldiğinden (yine de kontrol edebilirsiniz) Daha sonra <strong>Start Commit</strong> diyoruz ve projemiz derlenip taranmaya başlıyor. Bunu <strong>Action</strong> sekmesinden görebiliyoruz.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cOGV3uqk7WrhQV8xVQy0fA.png" /></figure><p>Taramamız bitti ve CodeQL taradığı 130 satır kodta (not olarak düşeceğim neden bu kadar az olduğunu) 1 tane yüksek güvenlik açığı tespit etti. Bunu da security sekmesinden kod analizi bölümünden görebiliriz. Çıkan bulguya <a href="https://github.com/gkhan496/vulnerable-spring-boot-application/security/code-scanning/1">buradan</a> erişebilirsiniz.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M8lW_VsM73oUdyt1xzlz3g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oxdrlgC_2VZ6kgh4PPE65w.png" /></figure><p>Not: Burada tüm satırları analiz etmemesinin bir çok nedeni olabiliyor ben akışı anlattığımdan başka projeler için denemedim fakat burada nedenlerine ulaşabilirsiniz.</p><blockquote>If your CodeQL analysis scans fewer lines of code than expected, there are several approaches you can try to make sure all the necessary source files are compiled.</blockquote><p><a href="https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow">Troubleshooting your advanced setup for CodeQL - GitHub Docs</a></p><p>Bu şekilde CodeQL aracını kullanmış olduk. Okudunuz için teşekkür ederim. İyi ve güvenli pazarlar diliyorum.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=624a74d420" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>