<?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 Azams- on Medium]]></title>
        <description><![CDATA[Stories by Azams- on Medium]]></description>
        <link>https://medium.com/@azams?source=rss-1efe16ce522------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8H7tstB642F5CHrv6B9A4A.jpeg</url>
            <title>Stories by Azams- on Medium</title>
            <link>https://medium.com/@azams?source=rss-1efe16ce522------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 22:42:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@azams/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[Stealthy Strategies: Advanced Dynamic Function Obfuscation]]></title>
            <link>https://medium.com/@azams/stealthy-strategies-advanced-dynamic-function-obfuscation-3aadc66b49ec?source=rss-1efe16ce522------2</link>
            <guid isPermaLink="false">https://medium.com/p/3aadc66b49ec</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[advanced-obfuscation]]></category>
            <category><![CDATA[variable-functions]]></category>
            <category><![CDATA[source-code-review]]></category>
            <category><![CDATA[hidden-backdoor]]></category>
            <dc:creator><![CDATA[Azams-]]></dc:creator>
            <pubDate>Sun, 16 Jun 2024 04:37:12 GMT</pubDate>
            <atom:updated>2024-06-17T03:31:54.292Z</atom:updated>
            <content:encoded><![CDATA[<h3>Stealthy Strategies: Advanced Dynamic Function Obfuscation Across Programming Languages</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/671/1*tULpkODHOfcUivHQNZS99g.png" /><figcaption>Advanced Dynamic Function Obfuscation Across Programming Languages</figcaption></figure><p>Dynamic function calls can add a layer of flexibility to programming, but they also pose significant security risks if misused. These calls can invoke both user-defined and built-in functions, making it essential to understand the nuances and potential dangers of using them. This article delves deep into the technical intricacies of dynamic function calls and explores advanced obfuscation techniques to make detection by static code scanners challenging. This information is tailored for engineers and security professionals who seek a profound understanding of these mechanisms.</p><h3>Introduction to Variable Functions</h3><p>Variable functions, or dynamic function calls, allow the name of a function to be stored in a variable and executed as if it were a direct function call. While this feature is powerful, it can be exploited if not carefully managed. In essence, dynamic function calls can transform a program’s flow based on runtime conditions, making code both flexible and, potentially, vulnerable.</p><pre>&lt;?php<br>$func = &#39;system&#39;;<br>$func(&#39;whoami&#39;);<br>?&gt;</pre><p>In this example, the function name <em>system</em> is stored in a variable <em>$func</em>, which is then called with the argument <em>whoami</em>.</p><h3>Positive Security Implications</h3><ol><li><strong>Protection Against Reverse Engineering</strong>:<br>Obfuscation makes it challenging for attackers to understand the logic and flow of your application by renaming variables, functions, and classes, inserting meaningless code, or using code restructuring techniques. For example, by renaming critical function names or using misleading variable names, you can deter attackers from easily identifying and exploiting vulnerabilities.</li><li><strong>Defense Against Automated Tools</strong>:<br>Many automated tools and static code analyzers rely on patterns and signatures to detect vulnerabilities. Obfuscated code can evade these tools by altering these patterns, thus making it harder for automated attacks to succeed. For example, tools that scan for known vulnerabilities or malware signatures may fail to detect malicious patterns hidden within obfuscated code, offering protection against automated attacks.</li><li><strong>Securing Sensitive Algorithms or Logic</strong>:<br>Obfuscation can protect sensitive algorithms, intellectual property, or proprietary business logic from being reverse engineered or copied by unauthorized parties. For example, encrypting critical algorithms or using obfuscation techniques to hide sensitive logic ensures that even if attackers gain access to the code, understanding its functionality remains challenging.</li></ol><h3>Negative Security Implications</h3><ol><li><strong>Obscured Malicious Intent</strong>:<br>While obfuscation is used to protect legitimate code, it can also obscure malicious intent if not applied transparently or ethically. For example, malicious actors might use obfuscation techniques to hide malware, backdoors, or other harmful code within applications, evading detection by security reviews or antivirus software.</li><li><strong>Increased Complexity</strong>:<br>Obfuscated code is inherently more complex, which can introduce unintended vulnerabilities or bugs. For example, code restructuring or excessive renaming can lead to logic errors or performance issues that are harder to diagnose and fix during development or maintenance.</li><li><strong>Compliance and Auditing Challenges</strong>:<br>Obfuscation can complicate compliance audits or lead to misunderstandings about the true functionality of the application. For example, in regulated industries like finance or healthcare, obfuscated code might raise concerns about transparency and adherence to security standards, requiring clear documentation and justification for its use.</li></ol><h3>Example Obfuscation Technique</h3><p>Below are advanced techniques to obfuscate dynamic function calls in various programming languages.</p><h4>PHP</h4><p>PHP allows dynamic function calls using variable functions. To obfuscate these calls, we can use string manipulations, array operations, or encoding schemes.</p><p><strong>Example:</strong></p><pre>&lt;?php<br>$partial1 = &#39;str&#39;; // you can obfuscate this if you want to<br>$partial2 = &#39;replace&#39;; // and also this one<br><br>$function = $partial1 . &#39;_&#39; . $partial2;<br>$function = $function(&#39;a&#39;, &#39;s&#39;, &#39;aymet&#39;);<br><br>$func = $function[0] . $function[1] . $function[0] . $function[4] . $function[3] . $function[2];<br>$func(&#39;whoami&#39;);<br>?&gt;</pre><p>For PHP, I have already created a bit more advanced example in the <a href="https://github.com/danielmiessler/SecLists/blob/master/Web-Shells/PHP/another-obfuscated-phpshell.php">SecLists repository</a>.</p><p><strong>NodeJS</strong><br>JavaScript treats functions as first-class citizens, making it easy to assign them to variables.<br>Example:</p><pre>text = &#39;father_pride&#39;.replaceAll(&#39;pride&#39;, &#39;process&#39;);<br>text = text.replace(&#39;father&#39;, &#39;child&#39;);<br>const { exec } = require(text);<br><br>let command = &#39;whoami&#39;;<br>let hide = exec;<br><br>hide(command, (error, stdout, stderr) =&gt; {<br>  if (error) {<br>    return;<br>  }<br>  console.log(stdout);<br>});</pre><h3>Conclusion</h3><p>Obfuscation techniques can make dynamic function calls more challenging to detect by static code scanners. While these methods can enhance flexibility and disguise potentially dangerous calls, they also pose significant risks if misused. Proper validation, whitelisting, and security auditing are essential to mitigate these risks. By understanding and carefully applying these techniques, engineers and security professionals can balance flexibility and security in their codebases.</p><p>Remember, obfuscation should not replace good security practices but rather complement them. Always prioritize clarity, maintainability, and robust security measures when developing software.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3aadc66b49ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Paypal.com — HTML Content Spoofing]]></title>
            <link>https://medium.com/@azams/paypal-com-html-content-spoofing-8448a1285bce?source=rss-1efe16ce522------2</link>
            <guid isPermaLink="false">https://medium.com/p/8448a1285bce</guid>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[akamai]]></category>
            <category><![CDATA[paypal]]></category>
            <dc:creator><![CDATA[Azams-]]></dc:creator>
            <pubDate>Mon, 27 Aug 2018 09:18:14 GMT</pubDate>
            <atom:updated>2018-08-28T03:42:19.668Z</atom:updated>
            <content:encoded><![CDATA[<p>Pada awalnya, hari Sabtu 14 April 2018 adalah merupakan hari yang biasa saja bagi saya. Bermain dengan keluarga, ngopi, membaca artikel, melakukan pentest terhadap sebuah aplikasi. Setelah selesai melakukan Penetration Testing menggunakan Burp Suite, kemudian saya melakukan transaksi Paypal (dengan menggunakan browser yang terkoneksi dengan Burp Proxy) untuk memperpanjang kontrak server yang saya sewa secara bulanan. Setelah melakukan pembayaran, saya mencoba untuk melihat fitur-fitur terbaru milik paypal dengan melakukan browsing di berbagai halaman milik Paypal sembari mencoba untuk mengumpulkan link hasil request ke website Paypal.</p><p>Setelah saya merasa cukup mengumpulkan link tersebut, saya mencoba untuk memasukkan beberapa link (yang saya anggap baru saya temukan) ke dalam active scan. Setelah mulai bosan membaca beberapa fitur &amp; artikel mengenai Paypal, saya melakukan Logout pada Paypal dan kemudian saya berniat menutup aplikasi Burp Suite (saya lupa bahwa saya sudah melakukan active scanning pada beberapa link), tapi ternyata…</p><blockquote>saya melihat sesuatu yang menarik dari hasil Active-Scanning Burp Suite, yaitu : <strong>Reflected response </strong>yang oleh Burp Suite dikategorikan sebagai Informational.</blockquote><p>Burp Suite melakukan Active-Scanning terhadap Paypal dan memberikan informasi bahwa pada URL <a href="https://www.paypal.com/businesswallet/mymoney?inframe=yes">https://www.paypal.com/businesswallet/mymoney?inframe=yes</a> merefleksikan input yang kita berikan pada parameter inframe. Tanpa saya pikir panjang, saya coba Copy URL tadi dan mencoba untuk membuka URL diatas. Tapi ternyata ketika saya membuka URL tadi, saya diarahkan (Response Code 302) menuju menu Login Paypal. Saya membandingkan response dari hasil Active Scanning dengan response yang baru saja saya dapatkan, dan ternyata hasilnya berbeda. Kemudian saya lanjutkan melakukan login.</p><p>Setelah melakukan login, kembali saya melakukan perubahan input pada parameter inframe dengan strings <strong>&lt;/(‘“azams’”)&gt;</strong>.<strong> </strong>Dari hasil response yang saya dapatkan setelah melakukan request perubahan input dari parameter inframe, saya mendapatkan hasil seperti ini :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/571/1*ennlq32BIlmGYDtH9sMtGQ.png" /><figcaption>Request perubahan value dari parameter inframe.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/434/1*qMY_iNLeFbHUhrlG38c_3g.png" /><figcaption>Response yang didapatkan.</figcaption></figure><p>Saya terkejut dan benar-benar tidak percaya. Bukan terkejut gembira, tapi terkejut aneh karena saya bisa menemukan hasil yang seperti ini padahal banyak orang yang berusaha untuk mencari celah keamanan di website milik Paypal. Kemudian saya lanjutkan dengan melakukan escaping tag Script dan mencoba untuk menggunakan berbagai tag html yang bisa memicu timbulnya XSS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/572/1*JG00-u2l7esRxkSMci2y5w.png" /><figcaption>Escaping Script tag dengan html tag tambahan.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/426/1*7h2T6X2ld8c5-ipPpb5V7w.png" /><figcaption>Response hasil escaping.</figcaption></figure><p>Kemudian saya melanjutkan untuk melakukan injeksi payload XSS. Akan tetapi ternyata tidak semudah yang saya bayangkan diawal. Saya melupakan bahwa Paypal memiliki WAF, yaitu <strong>Akamai</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*RgqgR6ToTxAZeHHsNN5oIw.png" /><figcaption>Akamai — Web Application Firewall</figcaption></figure><p>Setelah mendapatkan hasil diatas, saya kembali ke fase kedua (fase pertama adalah ngopi) pentest yaitu Information Gathering (karena saya memang belum melakukannya). Dan berikut adalah yang saya dapatkan :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/596/1*LXhQt_OVVQCVdOLSOpzWEg.png" /><figcaption>Error Paypal — NodeJS</figcaption></figure><p>Dari error diatas, saya mendapatkan informasi bahwa Paypal menggunakan NodeJS.</p><p>Dari pengalaman saya melakukan Penetration Testing pada aplikasi NodeJS, saya sering mendapati bahwa aplikasi NodeJS memiliki kemungkinan untuk rentan terhadap HTTP Parameter Pollution (yang bisa dimanfaatkan untuk bypass WAF), seperti apa yang tertulis di diskusi <a href="https://stackoverflow.com/questions/30672500/what-is-http-parameter-pollution-attack-in-nodejs-expressjs">StackOverflow</a> ini. Kemudian saya mencoba untuk melakukan percobaan tersebut :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/569/1*XP1AdNTcSSsTtH7CprBmhQ.png" /><figcaption>Paypal — HTTP Parameter Pollution Request.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/433/1*3LB2ezdliEWuH4Htz-4KRA.png" /><figcaption>Paypal — HTTP Parameter Pollution Response.</figcaption></figure><p>Setelah mendapatkan hasil diatas, saya melanjutkan untuk mencoba menggunakan berbagai payload XSS untuk melakukan bypass terhadap WAF Akamai. Akan tetapi saya tetap tidak dapat melakukan bypass. :(<br>Akamai melakukan blocking pada string :</p><p><em>onerror,src,onload,&lt;script,onpageload, dan lain sebagainya..</em></p><p>Akhirnya saya menyerah dan beralih dari XSS ke HTML Content Spoofing.</p><p>Dari beberapa saat saya berjibaku dengan Akamai, akhirnya saya mendapatkan hasil seperti dibawah ini :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/763/1*Dg7LD6oZnh54DZUwN3kbHA.png" /><figcaption>Paypal — HTML Content Spoofing.</figcaption></figure><p>Kemudian saya mengirimkan report tanpa melakukan PoC secara menyeluruh (karena masih ada kewajiban di pekerjaan) karena saya pikir saya harus melakukan information gathering lagi untuk mencari request yang menggunakan application/form (mayoritas paypal menggunakan json request) untuk kemudian bisa digunakan untuk PoC lanjutan dari kerentanan tersebut. Pada tanggal 18 april 2018 saya mendapatkan balasan dari hasil report saya dan ternyata hasilnya adalah Duplicate Report (sudah saya duga sebelumnya, hahaha).</p><p>Sekian bahasan dari saya,</p><p>Happy hunting, experience first before bounty.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8448a1285bce" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>