<?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[mobis3c - Medium]]></title>
        <description><![CDATA[Let us protect smartphones, tablets, laptops and other portable computing devices, and the networks they connect to, from threats and vulnerabilities associated with wireless computing. - Medium]]></description>
        <link>https://medium.com/mobis3c?source=rss----4c239d101563---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>mobis3c - Medium</title>
            <link>https://medium.com/mobis3c?source=rss----4c239d101563---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:16:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/mobis3c" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Introduction to Symbolic Execution: How It Works, Tools & a Practical Angr Walkthrough]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/mobis3c/introduction-to-symbolic-execution-how-it-works-tools-a-practical-angr-walkthrough-0acd3e30ab62?source=rss----4c239d101563---4"><img src="https://cdn-images-1.medium.com/max/1400/0*h6wUXZ6PpOvFOIEX" width="1400"></a></p><p class="medium-feed-snippet">Imagine a bug in a large codebase that only shows up when two variables meet in a rare condition&#x200A;&#x2014;&#x200A;you never hit it through fuzzing or&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/mobis3c/introduction-to-symbolic-execution-how-it-works-tools-a-practical-angr-walkthrough-0acd3e30ab62?source=rss----4c239d101563---4">Continue reading on mobis3c »</a></p></div>]]></description>
            <link>https://medium.com/mobis3c/introduction-to-symbolic-execution-how-it-works-tools-a-practical-angr-walkthrough-0acd3e30ab62?source=rss----4c239d101563---4</link>
            <guid isPermaLink="false">https://medium.com/p/0acd3e30ab62</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[reverse-engineering]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Sanatsu]]></dc:creator>
            <pubDate>Fri, 01 May 2026 12:19:32 GMT</pubDate>
            <atom:updated>2026-05-01T12:19:31.143Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Exploiting Android’s Task Hijacking]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/mobis3c/android-task-hijacking-6a3a8848f16e?source=rss----4c239d101563---4"><img src="https://cdn-images-1.medium.com/max/600/1*uejmkc_uyVw6Z8cLlYE2qw.png" width="600"></a></p><p class="medium-feed-snippet">Introduction</p><p class="medium-feed-link"><a href="https://medium.com/mobis3c/android-task-hijacking-6a3a8848f16e?source=rss----4c239d101563---4">Continue reading on mobis3c »</a></p></div>]]></description>
            <link>https://medium.com/mobis3c/android-task-hijacking-6a3a8848f16e?source=rss----4c239d101563---4</link>
            <guid isPermaLink="false">https://medium.com/p/6a3a8848f16e</guid>
            <category><![CDATA[android-security]]></category>
            <category><![CDATA[task-hijacking]]></category>
            <category><![CDATA[task-hijack]]></category>
            <category><![CDATA[android-task-hijacking]]></category>
            <category><![CDATA[exploiting-task-hijacking]]></category>
            <dc:creator><![CDATA[Sanatsu]]></dc:creator>
            <pubDate>Fri, 08 Apr 2022 08:12:15 GMT</pubDate>
            <atom:updated>2025-07-25T05:55:07.583Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Automating Report Generation for Infosec People]]></title>
            <link>https://medium.com/mobis3c/automating-report-generation-for-infosec-people-de231b51e232?source=rss----4c239d101563---4</link>
            <guid isPermaLink="false">https://medium.com/p/de231b51e232</guid>
            <category><![CDATA[automated-reporting]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[mobis3c]]></category>
            <category><![CDATA[ms-word-template]]></category>
            <dc:creator><![CDATA[renparth]]></dc:creator>
            <pubDate>Tue, 31 Aug 2021 20:01:55 GMT</pubDate>
            <atom:updated>2021-08-31T20:05:15.486Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fwld8aKK_NwN4jQHPkLmSg.png" /><figcaption>Autogen process</figcaption></figure><p>While doing security assessments( VAPT), we had a single report format, However, we had to make reports manually for each and every project from scratch, even when the same set of vulnerabilities were repeated for different projects.</p><p>Hence, we had a thought of reducing the time taken for this redundant process and spend the spare time elsewhere useful by automating this report making process.</p><p>If you can’t wait for us to explain how and what we did, you can directly try out the <a href="https://github.com/ari5ti/security-report-generator">autogen</a>.</p><h3>First XLSX File (Knowledge Base)</h3><p>We had an idea to maintain a Knowledge Base(KB) in google sheets or excel which contains the list of vulnerabilities along with details(Title, Description, Impact, Risk etc) found during the security assessment and assign an identifier, such as MOB_VULN_1, MOB_VULN_2,… for each vulnerability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IsE8gLVBuFrtM9X38xlGNA.png" /><figcaption>Knowledge Base XLSX File</figcaption></figure><blockquote><strong>Note:</strong></blockquote><blockquote><strong>Add the vulnerability details severity wise (From CRITICAL to LOW) in the Knowledge Base XLSX file. This way the details are added to the final word report in the given exact order.</strong></blockquote><p>The columns are as explained below:</p><ul><li><strong>id</strong>— An associated ID of the vulnerability</li><li><strong>Vulnerability </strong>— Title of the vulnerability</li><li><strong>Risk, Impact, Likelihood</strong>— Rated from CRITICAL to LOW</li><li><strong>descrp </strong>— Description of the vulnerability</li><li><strong>imp </strong>— Actual impact of the issue</li><li><strong>recommendation </strong>— Fix for the issues.</li><li><strong>info</strong>- any additional info or references for the issue.</li></ul><p>In this way, new vulnerabilities found during each security assessment can be added to the KB to keep it up-to-date.</p><h3>Second XLSX File (Vulnerability ID, POC, CAPTION)</h3><p>During testing, a xlsx file named vuln.xlsx is created to maintain the list of associated IDs, POC and its caption in 3 separate columns for each finding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*kmFwnf5bUPGNe9KR6TJXlQ.png" /><figcaption>Vulnerability ID xlsx File</figcaption></figure><ul><li><strong>id </strong>— Associated IDs of each vulnerability from the Knowledge Base.</li><li><strong>poc</strong> — contains image names of the findings, separated by a pipe symbol (‘|’) . The images of all findings during the assessment are stored in a <strong>folder</strong> called <strong>poc</strong> (more on this later).</li><li><strong>cap</strong> — contains caption of each image separated by ‘|’ like POC. <strong>For Ex:</strong> from the above image, the caption for “insec_deeplink_1&quot; image is codeblock_1 and caption for “insec-deeplink_2” image is codeblock_2.</li></ul><h3>Template</h3><p>This is your Docx template file of security report. It contains placeholders for general details such as Client name, Vendor name, Service ..etc as well as placeholders for vulnerability details such as vulnerability title, description, POC, Remediation etc.</p><blockquote><strong>NOTE:</strong></blockquote><blockquote>Use only 1 version of word to create and use the template, using multiple word versions may generate unknown characters.(ex: creating template using word 2019 and using the autogen with word 2016 installed).</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*HKghKymJXkCuBT0X-ZF1pQ.png" /><figcaption>Placeholders for general details</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/605/1*B7fWHZPI0GnI-1myycjtbQ.png" /><figcaption>Placeholders for vulnerability details</figcaption></figure><p>In the above image, 1 and 2 are the for loops to loop through all vulnerabilities and its images(POC).</p><h3>Generate Report</h3><p>Before generating the report make sure you have all the required files in a single folder.</p><p>In the <strong>poc</strong> folder, place all screenshots of all the findings. Also make sure that the image names in poc folder match with the vuln.xlsx’s POC column.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/322/1*eVoueu6y5sB9hYBWLudilg.png" /><figcaption>Final Directory Structure</figcaption></figure><p>Clone and run the autogen.py</p><pre>pip install python-docx docxptl<br>git clone https://github.com/ari5ti/security-report-generator.git<br>python autogen.py</pre><p>Provide the required input like shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QAKffyn2l45O5F8PGm0n2Q.png" /><figcaption>autogen.py in action</figcaption></figure><h4>Final Result</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FzcJPKtil-Gc%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DzcJPKtil-Gc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FzcJPKtil-Gc%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7d8f613bb48f450a55b7be27ab018452/href">https://medium.com/media/7d8f613bb48f450a55b7be27ab018452/href</a></iframe><h3>Adding more placeholders</h3><p>If u need any new placeholders other than the existing ones, then alter code in (context &amp; user_input function),template.docx.</p><p>For ex:</p><p>In template.docx, to add a placeholder that displays document version then add {{ docversion }}.</p><p>In <strong>user_input</strong> function, make the <strong>ver</strong> variable as global. In autogen.py context, add <strong>docversion</strong> placeholder as shown below.</p><pre>context = {<br>        &#39;docversion&#39;: ver,<br>        }<br>        <br>def user_input():<br>    global ver<br>    ver = input(&quot;Enter document version: &quot;)</pre><p>The context is a dictionary data structure, so it maintains a key : value format.</p><p>Ex:<strong> docversion </strong>is the placeholder used in the template and <strong>ver</strong> is the value to be replaced with.</p><ul><li>if you do not need to use certain placeholders provide blank input for autogen.py.</li></ul><p><strong>NOTE: </strong>if you have any suggestion or questions about the <a href="https://github.com/ari5ti/security-report-generator">autogen</a>, please feel free to connect with us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de231b51e232" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mobis3c/automating-report-generation-for-infosec-people-de231b51e232">Automating Report Generation for Infosec People</a> was originally published in <a href="https://medium.com/mobis3c">mobis3c</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deep Link Exploitation: Introduction & Open/unvalidated Redirection]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/mobis3c/deep-link-exploitation-introduction-open-unvalidated-redirection-b8344f00b17b?source=rss----4c239d101563---4"><img src="https://cdn-images-1.medium.com/max/600/1*hqpprD4Ns76Z1pvrlaCcTA.png" width="600"></a></p><p class="medium-feed-snippet">Exploiting open/unvalidated Redirection.</p><p class="medium-feed-link"><a href="https://medium.com/mobis3c/deep-link-exploitation-introduction-open-unvalidated-redirection-b8344f00b17b?source=rss----4c239d101563---4">Continue reading on mobis3c »</a></p></div>]]></description>
            <link>https://medium.com/mobis3c/deep-link-exploitation-introduction-open-unvalidated-redirection-b8344f00b17b?source=rss----4c239d101563---4</link>
            <guid isPermaLink="false">https://medium.com/p/b8344f00b17b</guid>
            <category><![CDATA[exploiting-deeplinks]]></category>
            <category><![CDATA[mobis3c]]></category>
            <category><![CDATA[android-security]]></category>
            <category><![CDATA[deeplink-exploitation]]></category>
            <category><![CDATA[deep-link-android]]></category>
            <dc:creator><![CDATA[Sanatsu]]></dc:creator>
            <pubDate>Tue, 20 Jul 2021 11:15:56 GMT</pubDate>
            <atom:updated>2021-07-20T11:35:38.994Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Exploiting Android WebView Vulnerabilities]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/mobis3c/exploiting-android-webview-vulnerabilities-e2bcff780892?source=rss----4c239d101563---4"><img src="https://cdn-images-1.medium.com/max/1217/1*eQE5lyBsWVyCRy2uIg6AHA.png" width="1217"></a></p><p class="medium-feed-snippet">What is WebView?</p><p class="medium-feed-link"><a href="https://medium.com/mobis3c/exploiting-android-webview-vulnerabilities-e2bcff780892?source=rss----4c239d101563---4">Continue reading on mobis3c »</a></p></div>]]></description>
            <link>https://medium.com/mobis3c/exploiting-android-webview-vulnerabilities-e2bcff780892?source=rss----4c239d101563---4</link>
            <guid isPermaLink="false">https://medium.com/p/e2bcff780892</guid>
            <category><![CDATA[android-security]]></category>
            <category><![CDATA[xs]]></category>
            <category><![CDATA[exploiting-webviews]]></category>
            <category><![CDATA[mobile-security]]></category>
            <category><![CDATA[stealing-tokens]]></category>
            <dc:creator><![CDATA[Sanatsu]]></dc:creator>
            <pubDate>Sun, 04 Apr 2021 05:12:00 GMT</pubDate>
            <atom:updated>2021-04-26T11:28:39.944Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Exploiting Apps vulnerable to Janus (CVE-2017–13156)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/mobis3c/exploiting-apps-vulnerable-to-janus-cve-2017-13156-8d52c983b4e0?source=rss----4c239d101563---4"><img src="https://cdn-images-1.medium.com/max/698/0*NRAdiAHwAC1yKO-O.png" width="698"></a></p><p class="medium-feed-snippet">Android Janus Vulnerability CVE-2017&#x2013;13156</p><p class="medium-feed-link"><a href="https://medium.com/mobis3c/exploiting-apps-vulnerable-to-janus-cve-2017-13156-8d52c983b4e0?source=rss----4c239d101563---4">Continue reading on mobis3c »</a></p></div>]]></description>
            <link>https://medium.com/mobis3c/exploiting-apps-vulnerable-to-janus-cve-2017-13156-8d52c983b4e0?source=rss----4c239d101563---4</link>
            <guid isPermaLink="false">https://medium.com/p/8d52c983b4e0</guid>
            <category><![CDATA[mobile-security]]></category>
            <category><![CDATA[janus-vulnerability]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[android-cve-2017-13156]]></category>
            <category><![CDATA[android-security]]></category>
            <dc:creator><![CDATA[Sanatsu]]></dc:creator>
            <pubDate>Fri, 26 Mar 2021 10:16:18 GMT</pubDate>
            <atom:updated>2021-03-26T10:16:18.546Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Insecure Data Storage: Insecure Logging & Storage]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/mobis3c/insecure-data-storage-insecure-logging-storage-bf50db1c4879?source=rss----4c239d101563---4"><img src="https://cdn-images-1.medium.com/max/900/0*35mJaLH5jFWd-JHx.jpg" width="900"></a></p><p class="medium-feed-snippet">Before we get started, make sure you have genymotion setup ready. if not follow this guide to setup &amp; configure the genymotion in Linux.</p><p class="medium-feed-link"><a href="https://medium.com/mobis3c/insecure-data-storage-insecure-logging-storage-bf50db1c4879?source=rss----4c239d101563---4">Continue reading on mobis3c »</a></p></div>]]></description>
            <link>https://medium.com/mobis3c/insecure-data-storage-insecure-logging-storage-bf50db1c4879?source=rss----4c239d101563---4</link>
            <guid isPermaLink="false">https://medium.com/p/bf50db1c4879</guid>
            <category><![CDATA[insecure-logging]]></category>
            <category><![CDATA[mobile-security]]></category>
            <category><![CDATA[insecure-data-storage]]></category>
            <category><![CDATA[android-security]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Sanatsu]]></dc:creator>
            <pubDate>Fri, 12 Feb 2021 04:12:36 GMT</pubDate>
            <atom:updated>2021-02-12T04:12:36.275Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Android Application Basics]]></title>
            <link>https://medium.com/mobis3c/android-application-basics-b4da5aaa3e68?source=rss----4c239d101563---4</link>
            <guid isPermaLink="false">https://medium.com/p/b4da5aaa3e68</guid>
            <category><![CDATA[android-security]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[renparth]]></dc:creator>
            <pubDate>Sat, 06 Feb 2021 16:44:34 GMT</pubDate>
            <atom:updated>2021-02-06T16:44:34.403Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vwqww0ZBqK3mtp18.jpg" /></figure><p>Android apps can be written using Kotlin, Java, and C++ languages. The Android SDK tools is used to compile the code written by the developer along with any data and resource files associated with the code into an APK, an <em>Android package</em>, which is an archive file with an .apk suffix.</p><p>One APK file contains all the contents of an Android app and is the file, Android-powered devices use to install the app.</p><p>Each Android app lives in its own security sandbox, protected by the following Android security features:</p><ul><li>The Android operating system is a multi-user Linux system in which each app is a different user. Ex: if 40 apps are installed in your mobile, then there are 40 users for your mobile.</li><li>By default, the system assigns each app a unique Linux user ID (the ID is used only by the system and is unknown to the app). Ex: for twitter the system may assign ID 10, Facebook → 12, Instagram → 13 so on. Only the system knows these IDs.</li><li>The system sets permissions for all the files in an app so that only the user ID assigned to that app can access them. Ex: ID no 12 can only access files related to Facebook app.</li><li>Each process has its own virtual machine (VM), so an app’s code runs in isolation from other apps. Ex: run ps -A in adb shell.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*eJ5kUrdAu9-RQM7q1kTIdw.png" /><figcaption>adb shell used to list all the processes running in the device.</figcaption></figure><ul><li>By default, every app runs in its own Linux process. The Android system starts the process when any of the app’s components need to be executed, and then shuts down the process when it’s no longer needed or when the system must recover memory for other apps.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*MI8Ap5b3YMJE-VV07FC7Sg.png" /><figcaption>process of twitter apk (com.twitter.android) is running as USER: u0_a48, having PID 5137.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/1*WsTxeI_YjHM4dYW3CDoeBQ.png" /><figcaption>After it is closed, the process is stopped.</figcaption></figure><p>The Android system uses the <strong><em>principle of least privilege</em></strong>. That is, each app, by default, has access only to the components that it requires to do its work and no more. This creates a very secure environment in which an app cannot access parts of the system for which it is not given permission.</p><p>But, there are ways through which an app, can share its data with other apps and also access system services:</p><ul><li><strong>Apps sharing same Linux user ID can access each other’s files</strong>:</li></ul><p>It’s possible to arrange for two apps to share the same Linux user ID, in which case they are able to access each other’s files. To conserve system resources, apps with the same user ID can also arrange to run in the same Linux process and share the same VM. The apps must also be signed with the same certificate.</p><ul><li><strong>Apps use system services such as location, camera and Bluetooth:</strong></li></ul><p>An app can request permission to access device data such as the device’s location, camera, and Bluetooth connection. The user has to explicitly grant these permissions.</p><h3><strong>Components of Application</strong></h3><p>App components are the essential building blocks of an Android app. Each component is an entry point through which the system or a user can enter your app. Some components depend on others.</p><p>There are four different types of app components:</p><ul><li>Activities</li><li>Services</li><li>Broadcast receivers</li><li>Content providers</li></ul><p><strong>Android Intent</strong> is the <em>message</em> that is passed between components such as activities, content providers, broadcast receivers and services</p><p><strong>Activities</strong></p><p>An <em>activity</em> represents a single screen with a user interface. It is the entry point for interacting with the user.</p><p>For example, an social media app might have one activity to post tweets, or images, another activity that shows a live feed, and another activity for chat.</p><p>These activities work together to form a cohesive user experience in the social media app, But each one is independent of the others. As such, a different app can start any one of these activities if the social media app allows it.</p><p>For example, a camera app can start the activity in the social media app to post images and allow the user to share a picture. An activity allows many key interactions between system and app including the following:</p><ul><li><strong>Tracking activities</strong>: To ensure that the system keeps running the process that is hosting the activity, it keeps track of what the user currently cares about (what is on screen).</li><li><strong>Prioritise Processes:</strong> Knowing that previously used processes contain things the user may return to (stopped activities), and thus more highly prioritise keeping those processes around.</li><li><strong>Kills inactive process:</strong> Helping the app handle having its process killed so the user can return to activities with their previous state restored.</li><li>Providing a way for apps to implement user flows between each other, and for the system to coordinate these flows. (The most classic example here being share.)</li></ul><p><strong>Services</strong></p><p>A <em>service</em> is a general-purpose entry point for keeping an app running in the background for all kinds of reasons. It is a component that runs in the background to perform long-running operations or to perform work for remote processes. A service does not provide a user interface.</p><p>For example, a service might play music in the background while the user is in a different app, or it might fetch data over the network without blocking user interaction with an activity. Another component, such as an activity, can start the service and let it run or bind to it in order to interact with it.</p><p>There are actually two very distinct semantics services tell the system about how to manage an app: Started services tell the system to keep them running until their work is completed.</p><p>This could be to sync some data in the background or play music even after the user leaves the app. Syncing data in the background or playing music also represent two different types of started services that modify how the system handles them:</p><ul><li><strong>User Aware Service</strong></li></ul><p>Ex: Music playback service, Here the app tells the system by saying it wants to be foreground with a notification to tell us about it.</p><ul><li><strong>User Unaware Service</strong></li></ul><p>Ex: A regular background service is not something the user is directly aware as running, so the system may allow the service to be killed (and then restarting the service sometime later) if it needs RAM for things that are of more immediate concern to the user.</p><p><strong>Broadcast receivers</strong></p><p>A <em>broadcast receiver</em> is a component that enables the system to deliver events to the app outside of a regular user flow, allowing the app to respond to system-wide broadcast announcements.</p><p>The system delivers broadcasts even to apps that aren’t currently running. for ex, I will set an alarm at 6 AM in the Clock app and close the app, It wants to schedule an alarm to post a notification to tell me to wake up at 6 AM. Now, the system delivers that alarm to a BroadcastReceiver of the clock app and then the app rings accordingly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*7uc9fzQ5Iy1lKAjttByMLQ.png" /></figure><p>An application has to register for intent to receive broadcasts from the system.</p><p>Broadcasts can be originated from both (system and apps):</p><ul><li>System broadcasts — for example, a broadcast announcing that the screen has turned off, the battery is low, or a picture was captured.</li><li>Apps broadcasts — for example, to let other apps know that some data has been downloaded to the device and is available for them to use.</li></ul><p><strong>Content providers</strong></p><p>A <em>content provider</em> manages a shared set of app data that you can store in the file system, in a SQLite database, on the web, or on any other persistent storage location that your app can access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U9H4CRv-jXYT-culNt1ToA.png" /></figure><p>Through the content provider, other apps can query or modify the data if the content provider allows it. For Ex: A camera app will store all the photos in file storage, now a social media app which already has file storage read access permission queries the content provider in order to access the photos taken by the camera app.</p><p>A content provider is an entry point into an app for publishing named data items, identified by a URI scheme. Apps have control over the definition of URIs. Other apps have to query the content provider using URI.</p><p>To query a content provider, an app can specify the query string in the form of a URI which has following format to access the data.</p><pre>&lt;prefix&gt;://&lt;authority&gt;/&lt;data_type&gt;/&lt;id&gt;</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4da5aaa3e68" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mobis3c/android-application-basics-b4da5aaa3e68">Android Application Basics</a> was originally published in <a href="https://medium.com/mobis3c">mobis3c</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting up an Android Pentesting Environment]]></title>
            <link>https://medium.com/mobis3c/setting-up-an-android-pentesting-environment-29991aa0c3f1?source=rss----4c239d101563---4</link>
            <guid isPermaLink="false">https://medium.com/p/29991aa0c3f1</guid>
            <category><![CDATA[environment-setup]]></category>
            <category><![CDATA[android-security]]></category>
            <category><![CDATA[mobile-security]]></category>
            <category><![CDATA[android-security-setup]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <dc:creator><![CDATA[Sanatsu]]></dc:creator>
            <pubDate>Thu, 04 Feb 2021 16:51:10 GMT</pubDate>
            <atom:updated>2021-09-12T13:04:09.259Z</atom:updated>
            <content:encoded><![CDATA[<p>Android pentesting requires a dedicated environment which provides access to a rooted android device and let us see how to setup easily by using free tools.</p><h3>Android Virtual Device</h3><p>We will be using AVD which is the default emulator provided by the <a href="https://developer.android.com/studio">android studio</a>. Download and perform default installation, once you arrive at this screen, select more actions and click on AVD Manager.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/808/1*FCJ1GpaE8XaqYeCtsJJCXg.png" /></figure><p>In avd manager, select the device and android version 10 i.e. api 29 and create the device and close the android studio and emulator.</p><p>In terminal, run ~/Android/Sdk/emulator/emulator @Android_10 -writable-system -selinux permissive -qemu -enable-kvm to launch the device.</p><p>In new tab, run the below commands to root the device.</p><pre>adb root<br>git clone <a href="https://github.com/0xFireball/root_avd">https://github.com/0xFireball/root_avd</a><br>cd root_avd<br>adb shell &quot;mount -t tmpfs -o size=15M tmpfs /system/xbin&quot;<br>adb shell &quot;cat /proc/mounts | grep /system/xbin&quot;<br>cd SuperSU/x86<br>adb push chattr chattr.pie libsupol.so su supolicy  /system/xbin/<br>cd ../../<br>adb install SuperSU/common/Superuser.apk<br>adb shell &quot;nohup /system/xbin/su 0 su --daemon &amp;&quot;<br>adb shell &quot;ps -ef | grep daemonsu&quot;</pre><p>Supersu will be installed in the device to manage root access, if you would like to know why we need to run the above commands check this <a href="https://anthony-f-tannous.medium.com/android-10-emulation-of-magisk-supersu-on-an-aosp-avd-de93ed080fad">detailed blog.</a></p><h3>Genymotion</h3><p>When starting out learning, android emulators are the great way to get experience with a variety of devices having different API levels without costing much and Genymotion provides exactly that with great User Experience and easy to configure nature for free.</p><blockquote><strong><em>Note:</em></strong><em> VirtualBox is used as a core by genymotion to virtualize Android operating systems. So please install VirtualBox in your system in order to proceed: </em><a href="https://www.virtualbox.org/wiki/Downloads"><em>link</em></a></blockquote><p>Genymotion requires user registration to use its dashboard and for that first you need to create an account: <a href="https://www.genymotion.com/account/create/">link</a></p><p>After completing your registration process download its installer from <a href="https://www.genymotion.com/download/">here</a> and install it in your host computer.</p><pre>#make it executable<br>chmod +x genymotion-3.2.X-linux_x64.bin</pre><pre>#specify installation path<br>./genymotion-3.2.X-linux_x64.bin -d &lt;Genymotion_install_path&gt;<br>cd &lt;Genymotion_install_path&gt;</pre><pre>#run from the installed path<br>./genymotion</pre><p>Once Genymotion is installed, you can sign in using your credentials specified in the registration process.</p><p>you can install a new device by clicking on plus icon at the top right corner and selecting your desired template and keep network mode Bridged</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/651/1*GDSLH64dvsK0Pww0xiEq8A.png" /></figure><blockquote>If some app contains ARM native code, then Genymotion will not be able to run the app as it consists of x86 (32-bit) architecture and will throw an error. You can avoid this problem by installing ARM translation library into emulated device: <a href="https://github.com/m9rco/Genymotion_ARM_Translation">link</a></blockquote><blockquote><strong><em>Note: </em></strong><em>At this point of time this library only supports up to android version 8.0 so download right package according to your emulated device’s specifications.</em></blockquote><p>Once the device is started, select wifi from genymotion options and select wifi to enable network emulation.</p><p>select OpenGapps to install Google apps Or in the case of <strong>Archive Error</strong> download gapps file manually from their official <a href="https://www.opengapps.org/">site</a> to your PC.</p><p>Before downloading, check the architecture of mobile, in the terminal run:</p><pre>sudo apt update<br>sudo apt install adb<br>adb shell<br>getprop | grep abi</pre><pre>#architecture can be found in []</pre><p>Download the exact gapps for the architecture from their site and extract the files in your system and then drag and drop the files to the device.</p><h3>Burp Suite</h3><p>Open Burpsuite and navigate to Proxy -&gt; Options. In proxy listeners section, click on add and in Binding section give the binding port and set bind to address to “all interfaces” and click ok.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*-qpQwcbxCLBcfePdhgzjxQ.png" /></figure><p>goto proxy and export the certificate as shown</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HshTDfiz_Y10wO2aKkvRhA.png" /><figcaption>cert export</figcaption></figure><pre>#check if device is connected<br>adb devices -l</pre><pre>#check for ip address<br>ip a</pre><p>In Android device, Go to Settings → Network &amp; Internet → WiFi and then Click on gear icon next to AndroidWifi. Now, Click on Edit button → Advanced Options → Proxy → Manual.</p><p>Add your system ip address in proxy hostname and bind port as port number and Save.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/434/1*1Z6ZdRJsZJ_lASBWO_fsgg.png" /></figure><p>Traditional way of installing burp cert wont work in recent android versions.</p><p>So we need to install the burp cert as system level cert to work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/648/1*XR6EhUgRkzMiyMTZd5v-VQ.png" /><figcaption>convert the ca</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*QctwUcawgpemoBKG98-qTA.png" /><figcaption>puch ca to device</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/547/1*SJUL9FcSTBfAQhJy7zTd1w.png" /><figcaption>install ca as system &amp; reboot</figcaption></figure><h3>APKTool</h3><p>A tool for reverse engineering 3rd party, closed, binary Android apps. It can decode resources to nearly original form and rebuild them after making some modifications. It also makes working with an app easier because of the project like file structure and automation of some repetitive tasks like building apk, etc.</p><ol><li>Download Linux <a href="https://raw.githubusercontent.com/iBotPeaches/Apktool/master/scripts/linux/apktool">wrapper script</a> (Right click, Save Link As apktool)</li><li>Download apktool-2 (<a href="https://bitbucket.org/iBotPeaches/apktool/downloads/">find newest here</a>)</li><li>Rename downloaded jar to apktool.jar</li><li>Move both files (apktool.jar &amp; apktool) to /usr/local/bin (root needed)</li><li>Make sure both files are executable (chmod +x)</li><li>Try running apktool via cli</li></ol><h3>APKSigner</h3><pre>sudo apt install -y apksigner</pre><h3>Jadx</h3><p>Command line and GUI tools for producing Java source code from Android Dex and Apk files</p><pre>git clone https://github.com/skylot/jadx.git<br>cd jadx<br>./gradlew dist<br>alias jadx-gui=&quot;~/jadx/build/jadx/bin/jadx-gui&quot;</pre><h3>PID Cat</h3><p><strong>Process ID (PID) Cat </strong>is a logcat script which only shows log entries for processes from a specific application package.</p><p>Installing PID Cat:</p><pre>#Download pidcat &amp; make it executable<br>sudo wget -O /usr/local/bin/pidcat <a href="https://raw.githubusercontent.com/JakeWharton/pidcat/master/pidcat.py">https://raw.githubusercontent.com/JakeWharton/pidcat/master/pidcat.py</a> &amp;&amp; sudo chmod +x /usr/local/bin/pidcat</pre><p>Check out <a href="https://medium.com/mobis3c/insecure-data-storage-clear-text-storage-of-sensitive-information-hard-coded-strings-fb7b056c0d0">Insecure Data Storage: Hardcoded secrets</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29991aa0c3f1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mobis3c/setting-up-an-android-pentesting-environment-29991aa0c3f1">Setting up an Android Pentesting Environment</a> was originally published in <a href="https://medium.com/mobis3c">mobis3c</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Insecure Data Storage: Clear Text Storage of Sensitive Information (Hard-coded strings…]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/mobis3c/insecure-data-storage-clear-text-storage-of-sensitive-information-hard-coded-strings-fb7b056c0d0?source=rss----4c239d101563---4"><img src="https://cdn-images-1.medium.com/max/1280/1*3cDLNfzWrV5aUr-4UlamFQ.png" width="1280"></a></p><p class="medium-feed-snippet">Before we get started, we need to have the apk which can be extracted from the device by installing the application through the play store&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/mobis3c/insecure-data-storage-clear-text-storage-of-sensitive-information-hard-coded-strings-fb7b056c0d0?source=rss----4c239d101563---4">Continue reading on mobis3c »</a></p></div>]]></description>
            <link>https://medium.com/mobis3c/insecure-data-storage-clear-text-storage-of-sensitive-information-hard-coded-strings-fb7b056c0d0?source=rss----4c239d101563---4</link>
            <guid isPermaLink="false">https://medium.com/p/fb7b056c0d0</guid>
            <category><![CDATA[insecure-data-storage]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[mobile-security]]></category>
            <category><![CDATA[hardcoded-in-apk]]></category>
            <category><![CDATA[android-security]]></category>
            <dc:creator><![CDATA[Sanatsu]]></dc:creator>
            <pubDate>Thu, 04 Feb 2021 16:49:04 GMT</pubDate>
            <atom:updated>2021-03-24T07:33:30.295Z</atom:updated>
        </item>
    </channel>
</rss>