<?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"><channel><title><![CDATA[Ilham Setiawan]]></title><description><![CDATA[Ilham Setiawan]]></description><link>https://ilhamsetiawan.web.id</link><generator>RSS for Node</generator><lastBuildDate>Tue, 07 Apr 2026 19:37:50 GMT</lastBuildDate><atom:link href="https://ilhamsetiawan.web.id/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[git Directory Exposure on apply.dinus.ac.id]]></title><description><![CDATA[Hello everyone,
I want to share a security finding on a registration website of one university in Indonesia. While inspecting their production environment, I discovered that the .git directory was still publicly accessible.
This poses a serious secur...]]></description><link>https://ilhamsetiawan.web.id/git-directory-exposure-on-applydinusacid</link><guid isPermaLink="true">https://ilhamsetiawan.web.id/git-directory-exposure-on-applydinusacid</guid><category><![CDATA[Security]]></category><category><![CDATA[Git]]></category><dc:creator><![CDATA[Ilham Adi Setiawan]]></dc:creator><pubDate>Thu, 29 May 2025 19:18:49 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1748546235357/b08f10e2-f92a-4178-80a7-67e5ff4c221e.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Hello everyone,</p>
<p>I want to share a security finding on a registration website of one university in Indonesia. While inspecting their production environment, I discovered that the <code>.git</code> directory was still publicly accessible.</p>
<p>This poses a serious security risk because an attacker could reconstruct the repository and extract sensitive information or credentials left in the development history.</p>
<p>During my validation and data extraction attempts, I was able to retrieve the application’s source code, critical credentials such as SMTP details, and even sensitive files like ID cards.</p>
<p><strong>Note:</strong> It is crucial to implement clean and automated deployment processes to prevent such exposures.</p>
<p>I have responsibly reported this issue to the relevant team, and it has since been resolved.</p>
<p><img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1748546451002/2fcb61f5-0874-4ce6-9b90-f48f50247815.png" alt class="image--center mx-auto" /></p>
]]></content:encoded></item></channel></rss>