<?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 Meridian Miftari on Medium]]></title>
        <description><![CDATA[Stories by Meridian Miftari on Medium]]></description>
        <link>https://medium.com/@meridianmiftari?source=rss-cc7f60a7a704------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*p7VuqEyORKyI0X8e.</url>
            <title>Stories by Meridian Miftari on Medium</title>
            <link>https://medium.com/@meridianmiftari?source=rss-cc7f60a7a704------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 13:41:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@meridianmiftari/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[From SSRF To AWS Credentials Disclosure]]></title>
            <link>https://infosecwriteups.com/from-ssrf-to-aws-credentials-disclosure-64c51e1bf5dc?source=rss-cc7f60a7a704------2</link>
            <guid isPermaLink="false">https://medium.com/p/64c51e1bf5dc</guid>
            <category><![CDATA[pentest]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[ssrf]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Meridian Miftari]]></dc:creator>
            <pubDate>Mon, 03 Jun 2019 13:25:03 GMT</pubDate>
            <atom:updated>2019-06-13T09:14:18.314Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi there, Info Sec Community</p><p>On this article I will describe an offensive method of attack in the security of a website, more exactly configured with Jira Software, identified with SSRF Vulnerability</p><p>Jira Software is a proprietary issue tracking product developed by Atlassian that allows bug tracking and agile project management.<br>So from a vulnerable Jira Software we will get AWS Instance Credentials</p><p>Below are the 5 attack stages we will take: From Reconnaissance to Command &amp; Control of AWS Instance</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K0thuuk2MZeKyf2d4bDt6w.png" /></figure><ol><li>Reconnaissance</li></ol><ul><li>Here we use nmap network scanner, so that we need to take more specific information on the product we are testing.</li><li>And it is telling that is hosted on Amazon Web Services, and there are 2 open ports : 80 HTTP &amp; 443 HTTPS</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ar2BHNowRX2rSXdm" /><figcaption>1</figcaption></figure><p>2. We open the IP in browser and the Jira Software Appears!</p><ul><li>As in any basic test that should be seen what the version contains a software product etc.<br>Jira here comes with a version 7.1.2</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*u7jxsxWyU0jeG_F_" /></figure><p>3. Researching about vulnerabilities on Jira Software</p><ul><li>Here we do some research about this version, and we see that all versions earlier than 7.3.6 are affected by the SSRF vulnerability.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6IC5x2a4fqMpO0-Q" /></figure><p>4. SSRF Vulnerability is found in the consumerUri = parameter</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Qp2Jyuk9DhDlWnV7" /></figure><p>5. Weaponization — Testing Vulnerability</p><ul><li>We test the parameter with an open redirect on the google.com site, where it works</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*brpF3iEFegitQSCX" /></figure><ul><li>Testing at other weaknesses enables us to create an open redirect that leads the creation of an XSS Payload to this parameter!</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WRAOlSVpTsgNUaq9" /></figure><p>6. Delivery — Delivering SSRF Attack on AWS Instance!</p><ul><li>We have to send the vulnerability to the AWS Instance, with exactly IP 169.254.169.254 that are relevant to Amazon’s services.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*R1HxhfU0fL_3NiHp" /></figure><p>7. Exploitation — Exploitation of AWS Instance, on parameter consumerUri=</p><ul><li>So it worked successfully and as we can see here, there is information about the instance like private IP, version, InstanceId etc.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ydlpEaWuus2m5kXu" /></figure><ul><li>Grabbing Credentials of AWS Instance<br>- We will attempt to get the AWS Instances Credentials, whereas can be seen the access key id and the secret access key that are fundamental to get access on it.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3dQwzFd1WYvV_Pg1" /></figure><p>8. Command &amp; Control — Configuration of AWS Instance</p><ul><li>apt update awscli</li><li>Here we will configure AWS CLI, in our terminal.</li><li>Exporting the credentials that we saw earlier.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ntw6oGxOKxcBmfIn" /></figure><p>9. Command &amp; Control — Getting Full Access on AWS!</p><ul><li>And finally after configuration, this enabled us to get access to AWS Instances, strictly in control of the website.</li><li>We could proceed further up to the upload of any shell, but all this testing was done in the client’s own proctoring, where which was enough to prove it and to further escalate with this weakness.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jjzUCbHGVoHALy0a" /></figure><p>11. Prevention ways — Some ways to not get affected by this vulnerability</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*_yU6VdBoCWddXe__hZHBtQ.png" /></figure><p>//Hope, you had a great time reading this write up, and learned new things.<br>//Thank you very much.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=64c51e1bf5dc" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/from-ssrf-to-aws-credentials-disclosure-64c51e1bf5dc">From SSRF To AWS Credentials Disclosure</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Responder to NT Authority\SYSTEM]]></title>
            <link>https://infosecwriteups.com/from-responder-to-nt-authority-system-39abd3593319?source=rss-cc7f60a7a704------2</link>
            <guid isPermaLink="false">https://medium.com/p/39abd3593319</guid>
            <dc:creator><![CDATA[Meridian Miftari]]></dc:creator>
            <pubDate>Thu, 03 Jan 2019 16:46:40 GMT</pubDate>
            <atom:updated>2020-12-07T18:09:13.255Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Hi there, my name is Meridian Miftari. I&#39;m 21 years old (Security Researcher) from Kosovo.<br>On this article I will talk or describe an offensive method of attacks in networks by using Responder &amp; SMB Impacket Tools</blockquote><blockquote>This attack that I will describe in fact it is known as man in the middle attack(MITM), this attack confronts with the idea why it&#39;s dangerous to give to others the password of the wireless.</blockquote><blockquote>This network pen testing was performed in an authorized environment of a Private Telecom Company, that for matter of confidentiality im not allowed to mention the name of the client!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hhf7d3EgPezLMgG0_71jXg.png" /></figure><blockquote>Here I will describe a short brief explanation of the features that this tool has, and those which we will use them.</blockquote><blockquote>Responder its an Offensive Security Tool that Red Teams use it, as we mentioned that its more a man in the middle attack, it has to do with intercepting the communication between 2 or more systems in a network.<br> <br><strong>Some features of the Tool</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1ti7sm1ChSNXAUUJv-5ZyQ.png" /></figure><blockquote>In the launching process, this is how the tool looks, I’ve executed in the wlan0 interface, and down we can see the built-in servers that this tool has</blockquote><blockquote>- Smb</blockquote><blockquote>- HTTP</blockquote><blockquote>- MySQL</blockquote><blockquote>- Kerberos etc.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T-QS4s1aLiTXA-4_e6KAqA.png" /></figure><blockquote>So after the execution of this tool, we see it sends requests in every computer inside that network, and in the end we see that the target has responded to us with his username along with the NTLMv2 Hash</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zQhUkdECcOVtH21omv8a7w.png" /></figure><blockquote>After we captured NTLMv2 Hash and decrypt it with the help of John the Ripper, that is a very well-known password cracker, the decryption process it depends on the complexity of the password that the system has.<br>After the cracking process is finished, we can see the decrypted password in the picture!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2mhfjcuFn10Yc8uXxIuJDw.png" /></figure><blockquote>After the cracking process, we will use Impacket packages. <br>Impacket is a collection of Python classes for working especially with network protocols, and one of them is smbclient.py</blockquote><blockquote>We will use the username &amp; password we got from John the Ripper Cracker to login to the disk shares of the system, as seen in the picture.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NGWmkCdUXekcCkpp41VRdw.png" /></figure><blockquote>We try to access the Administrator Shares of the system, however an error appears : Access Denied.<br>It means we have restricted access to them.!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2la1udXtAuO-N4jBYXSmMw.png" /></figure><blockquote>Further we will 2 other scripts, that are part of Impacket Packages that we mentioned earlier.<br>Rpcclient.py &amp; GetUserspns.py</blockquote><blockquote>Rpcclient.py : This script its default installed in Kali Linux, we will use to enumerate domains with the Username &amp; Password of the system.</blockquote><blockquote>GetUserSPNs.py : This script will try to find and fetch Service Principal Names that are associated with normal user accounts.</blockquote><blockquote>(SPN) are unique identifiers of a service instance in, are used by Kerberos authentication to associate a <strong>service</strong> instance with a <strong>service</strong> logon account, and they hold a TGT(Ticket Granting Ticket)that is a small, encrypted identification file with a limited validity period.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fZPX4TCKCiw-koOJAg5Zig.png" /></figure><blockquote>After getting the valid TGT, we decrypt using the help of Hashcat that is also a very well-known password cracker.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ucv3l8y3SHPBCJy6XFUAPg.png" /></figure><blockquote>In the end after we get the password of the Administrator, we will login to it, and we escalated our privileges from Simple User to NT Authority\SYSTEM</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*696ASVA1MhIXHt2b_m4xzw.png" /></figure><blockquote>Prevention Ways by this attack are described in the picture.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*id90VZA8D3kdXFELeEZlRQ.png" /></figure><p>//Hope, you have a great time reading this writeup and learned new things<br>//Thank you very much.</p><p>Tools :</p><ul><li><a href="https://github.com/SpiderLabs/Responder">GitHub - SpiderLabs/Responder: Responder is a LLMNR, NBT-NS and MDNS poisoner, with built-in HTTP/SMB/MSSQL/FTP/LDAP rogue authentication server supporting NTLMv1/NTLMv2/LMv2, Extended Security NTLMSSP and Basic HTTP authentication.</a></li><li><a href="https://github.com/SecureAuthCorp/impacket">GitHub - fortra/impacket: Impacket is a collection of Python classes for working with network protocols.</a></li><li><a href="https://github.com/hashcat">hashcat</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39abd3593319" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/from-responder-to-nt-authority-system-39abd3593319">From Responder to NT Authority\SYSTEM</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Accessing Public & Private Keys in a Blockchain Website]]></title>
            <link>https://infosecwriteups.com/how-i-was-able-to-access-any-public-private-keys-in-a-blockchain-website-ae0346da91bb?source=rss-cc7f60a7a704------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae0346da91bb</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[idor]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[vulnerability]]></category>
            <dc:creator><![CDATA[Meridian Miftari]]></dc:creator>
            <pubDate>Tue, 27 Mar 2018 18:12:05 GMT</pubDate>
            <atom:updated>2020-12-07T18:20:16.658Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi there<br>My name is Meridian Miftari, Im a Security Researcher from Kosovo. <br>Today i’ll share my first writeup about finding an IDOR vulnerability , in a Blockchain Website, that allowed me to view any users data, such as including public &amp; private keys &amp; names ect.</p><blockquote>Insecure Direct Object Reference (called IDOR from here) occurs when a application exposes a reference to an internal implementation object.It means it allows us to access unauthorized data due to exposed reference.</blockquote><p>I have illustrated an IDOR Vulnerability in the following graph , between user &amp; server.<br>For the matter of confidentiality i will not share the Program Name.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/833/1*F2SmzCKNTQTil8jwoK5HpQ.png" /></figure><p>The main thing to do is to get as much information as possible for the web application structure . I started mapping the application , and finding as many endpoints as possible. <br>So got one that looked promising , tried (“,’) and other different payloads for Sql Injection, but it just appeared the same error, nothing sensitive at response!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eDFfdD0Ybm1qZ8OEswfcEg.png" /></figure><p>Next one, I founded an endpoint : ?keyword={} .<br>So I said let’s give it a try.<br>First i tried to fuzz the endpoint with different parameters, numbers ect, nothing happened at all.<br>Took a break to refresh my mind, so came back, thought to try to leave the ?keyword={} blank and suddenly something interesting appeared!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_oAKN4Mh_cLmdwLjZXN3_Q.jpeg" /></figure><p>I sended this directly to Intruder for Fuzzing , specified parameter ?keyword=<br>and than i used random different payloads for words such as : a , b, c , d.<br>It seemed it was sort of username enumeration.</p><p>Request:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tg0PR-c_Ua_I-l_ZsnxwcQ.png" /></figure><p>Not sure how the application handled the random payloads, but suddenly the web application, started showing more sensitve data, not only that i could view the usernames but also their public &amp; private keys for their wallets!</p><p>Response:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g6aXHVIn2hrSQBEH9UfKbA.jpeg" /></figure><p>//Hope, you have a great time reading this writeup , and learned new things.<br>//Thank you very much.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae0346da91bb" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/how-i-was-able-to-access-any-public-private-keys-in-a-blockchain-website-ae0346da91bb">Accessing Public &amp; Private Keys in a Blockchain Website</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>