<?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 rad0v on Medium]]></title>
        <description><![CDATA[Stories by rad0v on Medium]]></description>
        <link>https://medium.com/@rad0v?source=rss-8c7153015c28------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*j99RZcxY6R8yVypo</url>
            <title>Stories by rad0v on Medium</title>
            <link>https://medium.com/@rad0v?source=rss-8c7153015c28------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 18:38:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rad0v/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[Solving Room “The Concierge Knows Too Much” (TryHackMe)]]></title>
            <link>https://rad0v.medium.com/solving-room-the-concierge-knows-too-much-tryhackme-02c496054b87?source=rss-8c7153015c28------2</link>
            <guid isPermaLink="false">https://medium.com/p/02c496054b87</guid>
            <category><![CDATA[tryhackme-walkthrough]]></category>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ai-security]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <dc:creator><![CDATA[rad0v]]></dc:creator>
            <pubDate>Sat, 01 Aug 2026 02:10:05 GMT</pubDate>
            <atom:updated>2026-08-01T02:10:05.885Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WfFLepZyOVaeDPPjyDJxtQ.png" /><figcaption>Room Image</figcaption></figure><p>This is a very easy room which involves Prompt Injection and LLM Security. I will be further attaching screenshots of how I completed this room.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/977/1*WormVuGH-XRorWo05jS2oA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/978/1*iDP06xM6cllh-e_LGL0Acg.png" /></figure><p>Notice how it detected the intrusion at high level.</p><p>Thanks to the AI Security roadmap there were ton of examples of breaking through this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/1*mzmOF-5_gkf5Ok2PBIfEnQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/737/1*vmX5l3F8IYYLGXauz6jIfA.png" /></figure><p>Hence the flag was —<strong> THM{v3r4_kn0ws_t00_much!}</strong></p><p>Thanks for reading! Please like and follow :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=02c496054b87" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Solving “Penetration Testing Frameworks” (TryHackMe)]]></title>
            <link>https://rad0v.medium.com/solving-penetration-testing-frameworks-tryhackme-099e1730613a?source=rss-8c7153015c28------2</link>
            <guid isPermaLink="false">https://medium.com/p/099e1730613a</guid>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[tryhackme-walkthrough]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[tryhackme]]></category>
            <dc:creator><![CDATA[rad0v]]></dc:creator>
            <pubDate>Sun, 24 May 2026 14:44:30 GMT</pubDate>
            <atom:updated>2026-05-24T14:44:30.586Z</atom:updated>
            <content:encoded><![CDATA[<p>Learn about the essential tools for passive reconnaissance, such as whois, nslookup, and dig.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U1b6oZXTmTtqj7IdyxbsZg.png" /></figure><h3>Introduction</h3><p>Without a structured approach, a penetration test quickly becomes a disorganized collection of random checks. You might miss critical attack surfaces, skip important documentation, or deliver findings that the client cannot act on. Worse, you might test systems that were never in scope and find yourself in legal trouble. This is exactly the problem that <strong>penetration testing frameworks</strong> solve.</p><p>Please note this is a not a walkthrough and is strictly for those who are stuck at finding the answers!</p><p>Room link: <a href="https://tryhackme.com/room/penetrationtestingframeworks">https://tryhackme.com/room/penetrationtestingframeworks</a></p><p><strong>Task 1 Answers:</strong></p><ol><li>Thoroughness</li><li>Compliance</li></ol><h3>OSSTMM</h3><p>You have probably heard the phrase “you can’t manage what you can’t measure.” In most engineering disciplines, quantification is a given: a structural engineer does not declare a bridge “safe” based on intuition. Yet in penetration testing, findings are often delivered as subjective narratives. The <strong>Open Source Security Testing Methodology Manual (OSSTMM)</strong> aims to change that.</p><p>Developed by the <strong>Institute for Security and Open Methodologies (ISECOM)</strong>, the <a href="https://www.isecom.org/OSSTMM.3.pdf">OSSTMM(opens in new tab)</a> (currently at <strong>version 3</strong>) applies the scientific method to security testing. Its defining characteristic is <strong>metrics over opinions</strong>: rather than delivering subjective risk judgments, OSSTMM produces quantifiable, verifiable, and repeatable results.</p><p><strong>Task 2 Answers:</strong></p><ol><li>Risk Assessment Values</li><li>Inquiry</li></ol><h3>OWASP WSTG</h3><p>You are testing a web application for an online retailer. The application handles user registration, product search, shopping cart, payment processing, and order tracking. Where do you even begin? Do you test the login form first? The search bar? The payment API? With dozens of potential attack surfaces in a single web application, it is easy to either test the same things twice or miss entire vulnerability classes altogether.</p><p>The <strong>Open Web Application Security Project (OWASP)</strong> addresses this problem with the <a href="https://owasp.org/www-project-web-security-testing-guide/">Web Security Testing Guide (WSTG)(opens in new tab)</a>. While OWASP is most widely known for the <a href="https://owasp.org/www-project-top-ten/">OWASP Top Ten(opens in new tab)</a> list of critical web vulnerabilities, the WSTG goes far deeper: it is a comprehensive, community-driven framework that organizes web application testing into <strong>over 90 discrete test cases</strong> grouped across twelve categories.</p><p><strong>Task 3 Answers:</strong></p><ol><li>WSTG-INPV</li><li>3</li></ol><h3>NIST SP 800–115</h3><p>Consider this scenario: you work as a security analyst for a government agency or a large enterprise that contracts with the federal government. Your organization needs a security assessment, but the results must satisfy auditors, comply with federal guidelines, and be defensible in the event of oversight inquiries. A penetration testing report full of informal commentary and subjective risk ratings won’t cut it. You need a methodology that federal regulators recognize and trust.</p><p>That is the niche filled by <a href="https://csrc.nist.gov/pubs/sp/800/115/final">NIST Special Publication 800–115(opens in new tab)</a>, titled <em>Technical Guide to Information Security Testing and Assessment</em>. Published by the <strong>National Institute of Standards and Technology (NIST)</strong>, this document provides a foundational framework for systematically evaluating the security posture of information systems. While it originated in the U.S. federal context, its principles are broadly applicable and widely adopted in the private sector, especially by organizations that value structured, repeatable processes.</p><p>NIST SP 800–115 is not a penetration testing framework in the narrow sense. It is broader: it covers the full spectrum of <strong>security testing and assessment techniques</strong>, from document reviews and log analysis to vulnerability scanning and full penetration tests. It treats penetration testing as one technique among several, all of which serve the goal of validating whether security controls work as intended.</p><p>Three core objectives drive the framework. First, <strong>identify vulnerabilities</strong> in systems, networks, and applications. Second, <strong>validate security controls</strong> by testing whether they perform as expected under adversarial conditions. Third, <strong>assess exploitability</strong> by simulating real-world attack scenarios to determine whether a threat actor can actually leverage identified weaknesses.</p><p><strong>Task 4 Answers:</strong></p><ol><li>Target vulnerability validation</li></ol><h3>PTES</h3><p>You have now seen frameworks that emphasize scientific metrics (OSSTMM), web application coverage (OWASP WSTG), and government-aligned assessment techniques (NIST SP 800–115). But here is a question worth considering: if you were hired tomorrow for a standard penetration testing engagement against a corporate network, which framework would most closely mirror the actual workflow you would follow from the first client call to the final report delivery?</p><p>For many working pentesters, the answer is the <strong>Penetration Testing Execution Standard (PTES)</strong>. Available at <a href="http://www.pentest-standard.org/">pentest-standard.org(opens in new tab)</a>, PTES was developed by a group of experienced security practitioners with a specific goal: to define what a real penetration test looks like, end-to-end. Where other frameworks focus on <em>what</em> to test or <em>how</em> to measure, PTES focuses on <em>how the engagement flows</em> from start to finish.</p><p>PTES is organized into <strong>seven phases</strong> that map directly to the lifecycle of a penetration testing engagement. This approach makes it exceptionally practical for junior testers because it answers the question that many frameworks leave implicit: “I have a signed contract; now what do I do on day one, day two, and every day after?”</p><p><strong>Task 5 Answers:</strong></p><ol><li>1</li></ol><h3>ISSAF</h3><p>Have you ever studied a vintage textbook and found that, despite its age, the core logic still holds up? In cyber security, tools and exploits have a short shelf life, but well-designed methodologies can outlast the technologies they were built to test. The <strong>Information Systems Security Assessment Framework (ISSAF)</strong> is a case in point.</p><p>Developed by the <strong>Open Information Systems Security Group (OISSG)</strong>, ISSAF is an open-source penetration testing framework designed to evaluate network, system, and application security. The latest version, <strong>ISSAF v0.2.1</strong>, was published around 2006, and the framework is <strong>no longer actively maintained</strong>. There is no longer an official URL to download it; however, the draft can still be found through archived sources online. This is important context: ISSAF’s methodology and phase structure remain instructive, but its tool-specific guidance is outdated and should not be relied upon for current engagements.</p><p><strong>Task 6 Answers:</strong></p><ol><li>Covering tracks</li></ol><h3>MITRE ATT&amp;CK</h3><p>In the previous tasks, we explored frameworks that tell you <em>how to conduct</em> a penetration test: how to scope it, progress through phases, and report your findings. But consider this situation: you have just completed an engagement using PTES, and the report documents that you gained initial access through a phishing email, escalated privileges by exploiting a misconfigured service, moved laterally using stolen credentials, and exfiltrated data through an encrypted channel. Your client reads the report and asks a deceptively simple question: “How does our exposure compare to what real threat actors are actually doing in the wild?”</p><p>That question is difficult to answer with a penetration testing framework alone. Frameworks like PTES and OSSTMM structure your testing process, but they do not systematically catalog the specific tactics and techniques that real-world adversaries use. This is the gap that <strong>MITRE ATT&amp;CK</strong> fills.</p><p><strong>ATT&amp;CK</strong> stands for <strong>Adversarial Tactics, Techniques, and Common Knowledge</strong>. Developed and maintained by <a href="https://attack.mitre.org/">MITRE Corporation(opens in new tab)</a>, it is not a traditional penetration testing framework. It is a <strong>knowledge base</strong> of adversary behavior, built from real-world observations of how threat actors operate. It catalogs <em>what</em> attackers do, organized in a structure that security professionals can use for threat intelligence, detection engineering, red teaming, and, relevant to this room, enriching penetration test findings.</p><p><strong>Task 7 Answers:</strong></p><ol><li>tactics</li><li>techniques</li><li>T1190</li></ol><h3>Other Notable Frameworks</h3><p>The frameworks we have covered so far, OSSTMM, OWASP WSTG, NIST SP 800–115, PTES, ISSAF, and MITRE ATT&amp;CK, represent the core methodologies and knowledge bases a junior penetration tester is most likely to encounter. But the landscape does not end there. Depending on the industry, platform, or regulatory environment your client operates in, you may need to be aware of more specialized frameworks that address specific domains.</p><p>This task surveys five additional frameworks. The goal is not deep mastery of each one but <strong>landscape awareness</strong>: knowing they exist, understanding their niche, and recognizing when a client engagement might call for one of them.</p><p><strong>Task 8 Answers:</strong></p><ol><li>PCI DSS Penetration Testing Guidelines</li><li>OWASP Mobile Application Security Testing Guide</li><li>CSA Cloud Control Matrix</li></ol><h3>Choosing the Right Framework</h3><p>You now have a working knowledge of several penetration testing frameworks, each with its own philosophy, structure, and strengths. But knowing what each framework <em>is</em> does not automatically tell you which one to <em>use</em>. In practice, framework selection is one of the first decisions a penetration tester makes after receiving an engagement brief, and it is a decision shaped by multiple factors that often pull in different directions.</p><p>Consider the analogy of a mechanic’s toolbox. A mechanic does not use every tool on every job; they select tools based on the vehicle, the problem, and the customer’s expectations. A penetration tester operates the same way. The “right” framework depends on the client’s industry, the type of systems being tested, the regulatory landscape, and the engagement’s objectives.</p><p><strong>Task 9 Answers:</strong></p><ol><li>NIST SP 800–115</li><li>WSTG,MASTG,PCI DSS</li></ol><h3>Conclusion</h3><p>We began with <strong>OSSTMM</strong> and its scientific, metrics-driven philosophy, where security is not a subjective opinion but a measurable property expressed through Risk Assessment Values. We then examined <strong>OWASP WSTG</strong>, the web application tester’s roadmap, with its 90+ test cases organized across the Software Development Life Cycle. <strong>NIST SP 800–115</strong> showed us how security testing fits into the government and enterprise world, structuring assessment techniques from passive document review through active exploitation. <strong>PTES</strong> brought us closest to the day-to-day reality of penetration testing, mapping seven phases from the first client call to the final report. <strong>ISSAF</strong>, though no longer maintained, gave us one of the clearest models of adversarial progression through its nine-step assessment. And <strong>MITRE ATT&amp;CK</strong> provided the common vocabulary for describing what adversaries actually do, enriching findings from any framework with technique IDs grounded in real-world threat intelligence.</p><p>We surveyed five additional frameworks, each serving a specialized niche, from mobile application testing (OWASP MSTG) to regulatory mandates in the payment card industry (PCI DSS) and the UK financial sector (CBEST). Finally, we practiced the applied skill of framework selection, recognizing that real engagements often require a primary methodology supplemented by domain-specific or regulatory frameworks.</p><p><strong>Task 10 Answers:</strong></p><ol><li>CBEST</li><li>No Answers Needed!</li></ol><p>And with this we are done with this room!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=099e1730613a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Solving “Cyber Kill Chain” (TryHackMe)]]></title>
            <link>https://rad0v.medium.com/solving-cyber-kill-chain-tryhackme-a26d1d5eb6b3?source=rss-8c7153015c28------2</link>
            <guid isPermaLink="false">https://medium.com/p/a26d1d5eb6b3</guid>
            <category><![CDATA[tryhackme-walkthrough]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[tryhackme-writeup]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[rad0v]]></dc:creator>
            <pubDate>Sun, 24 May 2026 14:12:07 GMT</pubDate>
            <atom:updated>2026-05-24T14:12:07.920Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H7hC83LdFGDJ91d5ZI05uw.png" /></figure><p>The Cyber Kill Chain room is a beginner-friendly SOC Level 1 room that explains how attackers perform cyber intrusions step-by-step using the Lockheed Martin Cyber Kill Chain framework.</p><p>Please note this is a not a walkthrough and is strictly for those who are stuck at finding the answers!</p><p>Room link: <a href="https://tryhackme.com/room/cyberkillchain">https://tryhackme.com/room/cyberkillchain</a></p><p><strong>Task 1 Answers:</strong></p><ol><li><strong>7</strong></li></ol><h3>Reconnaissance</h3><p>This is the information-gathering phase. Attackers collect details about the target using techniques like:</p><ul><li>OSINT</li><li>Google Dorking</li><li>Email harvesting</li><li>Social engineering</li></ul><p>Types:</p><ul><li><strong>Passive Reconnaissance</strong></li><li><strong>Active Reconnaissance</strong></li></ul><p><strong>Task 2 Answers:</strong></p><ol><li><strong>Google Dorking</strong></li><li><strong>passive reconnaissance</strong></li></ol><h3>Weaponization</h3><p>Here, the attacker prepares the payload. This could include:</p><ul><li>Malware</li><li>Malicious Office documents</li><li>Backdoors</li><li>Exploit kits</li></ul><p>One important concept in this phase is <strong>macros in Microsoft Office files</strong>, which attackers often abuse for malicious code execution.</p><p><strong>Task 3 Answers:</strong></p><ol><li><strong>Obfuscation</strong></li><li><strong>Macro</strong></li></ol><h3>Delivery</h3><p>The payload is sent to the victim through methods such as:</p><ul><li>Phishing emails</li><li>USB devices</li><li>Malicious websites</li><li>Watering hole attacks</li></ul><p><strong>Task 4 Answers:</strong></p><ol><li><strong>Malvertising</strong></li><li><strong>Smishing</strong></li></ol><h3>Exploitation</h3><p>The malware or exploit executes by abusing a vulnerability in the victim system.</p><p>One key topic here is:</p><ul><li>Zero-Day vulnerabilities</li></ul><p>These are vulnerabilities unknown to vendors at the time of exploitation.</p><p><strong>Task 5 Answers:</strong></p><ol><li><strong>Zero-day exploit</strong></li><li><strong>MFA</strong></li></ol><h3>Installation</h3><p>After exploitation succeeds, attackers establish persistence.</p><p>Some techniques include:</p><ul><li>Registry Run Keys</li><li>Startup folders</li><li>Web shells</li></ul><p><strong>Task 6 Answers:</strong></p><ol><li><strong>web shell</strong></li><li><strong>allowlisting</strong></li></ol><h3>Command &amp; Control (C2)</h3><p>Once persistence is achieved, the compromised machine communicates with the attacker’s infrastructure.</p><p>Common C2 methods:</p><ul><li>HTTP/HTTPS beaconing</li><li>IRC</li><li>DNS tunneling</li></ul><h4>DNS Tunneling</h4><p>The victim continuously communicates with attacker-controlled DNS servers to bypass traditional detection methods.</p><p><strong>Task 7 Answers:</strong></p><ol><li><strong>DNS tunnelling</strong></li><li><strong>HTTPS</strong></li></ol><h3>Actions on Objectives</h3><p>This is the final stage where the attacker achieves their goal:</p><ul><li>Data theft</li><li>Ransomware deployment</li><li>Lateral movement</li><li>Credential dumping</li><li>System destruction</li></ul><p>At this point, the compromise becomes extremely dangerous for the organization.</p><p><strong>Task 8 Answers:</strong></p><ol><li><strong>Data Exfiltration</strong></li><li><strong>principle of least privilege</strong></li><li><strong>Ransomware</strong></li></ol><h3>Conclusion</h3><p>Offensive security teams, such as penetration testers or red teamers, need to follow the steps of real adversaries to ensure that their attack simulation is realistic. This allows the company to test its defences and learn whether existing security controls are effective and how well its team can detect such an attack.</p><p><strong>Task 9 Answers:</strong></p><ol><li><strong>THM{CKC_NJHERDX327}</strong></li><li>No Answers Needed</li></ol><p>And with this we are done with this room!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a26d1d5eb6b3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Solving “Dive Into Pentesting” TryHackMe]]></title>
            <link>https://rad0v.medium.com/solving-dive-into-pentesting-tryhackme-6ec0bd77da0a?source=rss-8c7153015c28------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ec0bd77da0a</guid>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[tryhackme-writeup]]></category>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[pentesting]]></category>
            <dc:creator><![CDATA[rad0v]]></dc:creator>
            <pubDate>Sat, 23 May 2026 11:33:39 GMT</pubDate>
            <atom:updated>2026-05-23T11:33:39.033Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cTZb28gQ2CHpDgnvGClelA.png" /></figure><h3>Introduction</h3><p>Penetration testing is a proactive security practice that helps organisations uncover weaknesses in their systems, applications, and networks before attackers can exploit them. The value of a penetration test continues to increase as modern environments become more complex. Testers that understand the fundamentals of penetration testing can produce meaningful results and effectively communicate risk to stakeholders.</p><p>This room introduces the core concepts that every aspiring penetration tester should be familiar with. It covers what penetration testing is and how it differs from malicious hacking, the areas of focus during a penetration test, and the relationship between vulnerability, threat, and risk. It also explores why vulnerabilities exist in the first place, the mindset and habits that shape effective testers, and the ethical principles that strengthens client relationships.</p><p>Room link: <a href="https://tryhackme.com/room/diveintopentesting">https://tryhackme.com/room/diveintopentesting</a></p><p><strong>Task 1 Answers:</strong></p><ul><li>No Answers Needed!</li></ul><h3>Penetration Testing vs Malicious Hacking</h3><p><strong>Penetration Tester:</strong></p><ul><li>Penetration testers operate with explicit written consent from the system owner.</li><li>Penetration testers operate within a clearly defined scope that is set by the organisation in order to protect critical systems.</li><li>Penetration testers aim for broad coverage and assess multiple areas of a system.</li><li>Penetration testers are accountable for their actions and the impact of their work, and are expected to act professionally at all times.</li></ul><p><strong>Malicious Attacker:</strong></p><ul><li>Attackers operate without consent and violate the rights and security of the organisation.</li><li>Attackers are not restricted by scope and will target anything that helps them achieve their goal.</li><li>Attackers focus on the quickest or most effective path to success, and often target systems and data that can provide financial benefit.</li><li>Attackers do not feel accountable for their actions and do not take responsibility for the damage that they cause.</li></ul><p><strong>Task 2 Answers:</strong></p><ul><li>pentesting</li><li>Penetration Tester</li><li>Attacker</li></ul><h3>Penetration Testing Focus Areas</h3><h3>Web Application Penetration Testing</h3><p>Web application penetration testing focuses on finding gaps and weaknesses in a web application. Testing is commonly performed from a user perspective by interacting with the application’s user interface and its APIs. The goal is to assess how the application handles user input, authentication, authorisation, sessions, and data processing. Weaknesses in web applications can have great impact on its users because web applications are usually exposed to the internet.</p><h3>Network Penetration Testing</h3><p>Network penetration testing focuses on finding vulnerabilities in the underlying infrastructure that connects systems together. Testing could be performed from an external or an internal user perspective.</p><p><strong>Task 3 Answers:</strong></p><ul><li>External</li><li>Session Management</li></ul><h3>Vulnerability, Threat and Risk</h3><h3>Vulnerability</h3><p>A vulnerability is a weakness or gap in an organisation’s environment that could be exploited to compromise the security of systems, data, or operations. While it does not cause harm on its own, it presents an opportunity for exploitation.</p><h3>Threat</h3><p>A threat is anything that can exploit a vulnerability and cause harm to an organisation’s environment. It represents a source of danger that can take advantage of a weakness to compromise the confidentiality, integrity, and availability of the organisation’s systems.</p><h3>Risk</h3><p>Risk is the potential damage that could occur if a threat successfully exploits a vulnerability. We can determine the overall risk of a vulnerability by combining the impact and likelihood of exploitation. In some cases, a vulnerability that may look harmless could cause significant risk if it affects critical systems. In contrast, a vulnerability that may look harmful could only cause minimal risk if it exists in an isolated environment.</p><p><strong>Task 4 Answers:</strong></p><ul><li>Mitigation</li><li>External-facing application</li></ul><h3>Common Causes and Resulting Vulnerabilities</h3><ul><li>Human Assumptions</li><li>Software Bugs</li><li>System Complexity</li><li>Over-Customisation</li><li>Technical and Design Flaws</li></ul><p><strong>Task 5 Answers:</strong></p><ul><li>Human Assumptions</li></ul><h3>The Pentester Mindset</h3><h4>Effective Mindset:</h4><ul><li>Understanding the system</li><li>Attention to detail</li><li>Constant curiosity</li><li>Prioritising critical areas</li><li>Thinking in context</li><li>Creative thinking</li></ul><h4>Ineffective Mindset</h4><ul><li>Rushing to exploitation</li><li>Ignoring context</li><li>Over-reliance on tools</li><li>Making assumptions</li><li>Tunnel vision</li><li>Blindly following a checklist</li></ul><p><strong>Task 6 Answers:</strong></p><ul><li>Rushing to exploitation</li><li>Maintaining good notes</li><li>Proactive communication</li></ul><h3>Ethics, Permission and Trust</h3><h3>Ethics</h3><p>Ethics in penetration testing is demonstrated by responsibly assessing systems that may contain sensitive data or critical functionalities. Ethical behaviour helps a penetration tester make responsible decisions throughout an assessment, ensuring that actions are intentional and justified.</p><h3>Permission</h3><p>Permission in penetration testing is established through formal authorisation and a clearly defined scope before executing an engagement. Obtaining proper authorisation ensures that all activities are approved by the organisation being assessed and align with their expectations and goals.</p><h3>Trust</h3><p>Organisations may initially be cautious when allowing external testers to assess their systems. However, many organisations rely on independent assessments by external parties to properly evaluate and improve their security posture. Therefore, establishing trust from the very beginning is valuable.</p><p><strong>Task 7 Answers:</strong></p><ul><li>Scope</li><li>Business impact</li><li>Sensitive data</li></ul><h3>Knowledge Recap</h3><p><strong>Task 8 Answers:</strong></p><ul><li>THM{L3t$_d1v3_1nt0_Pen7es71ng!}</li></ul><p>And with this the room is done!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ec0bd77da0a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Solving “Guided Pentest: Infrastructure” (TryHackMe)]]></title>
            <link>https://rad0v.medium.com/solving-guided-pentest-infrastructure-tryhackme-4666bef4205f?source=rss-8c7153015c28------2</link>
            <guid isPermaLink="false">https://medium.com/p/4666bef4205f</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[tryhackme-writeup]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <dc:creator><![CDATA[rad0v]]></dc:creator>
            <pubDate>Fri, 22 May 2026 18:34:06 GMT</pubDate>
            <atom:updated>2026-05-22T18:34:06.170Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AE6zfMER3EWJRf7bbF29Qg.png" /></figure><p>I’ll be covering the answers and walkthrough for this room. So buckle up and let’s dive in.</p><p>Disclaimer! This writeup is for those people who are stuck in this room and not able to navigate further.</p><p><strong>Task 1 </strong>is easy just start up the target VM and attack box. I’ll be using Kali Linux box for this room.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/1*Ldn2jn1SyuCxXn267h68Tw.png" /></figure><h3>Enumeration</h3><p>Before you touch a single exploit or try a single password, you need to understand what you’re looking at. Enumeration is the foundation of every penetration test and, without it, you’re just guessing. The goal here is simple: learn as much as you can about the target before making any moves. What ports are open? What services are running? What versions are behind them? Every piece of information you gather now shapes the decisions you’ll make later. Rushed enumeration leads to missed opportunities, and in a real engagement, that could mean the difference between a finding and a footnote in your report.</p><p>Command : nmap -sV -sC -oN scan.txt IP</p><p><strong>Task 2 Answers:</strong></p><ul><li>6667</li></ul><h3>Vulnerability Analysis</h3><p>Your Nmap output gave you two open ports. The simplest method here is to Google their versions and the keyword “exploit”.</p><p>For example, Googling “OpenSSH 9.6p1 exploit” might yield results on theoretical or very distribution-specific exploits, but nothing tangible. So it is most likely a dead end.</p><p>If you are comfortable with the Kali packages, instead of googling, you can use the searchsploit utility to find exploits. Searchsploit is a command-line tool that lets you search Exploit-DB’s offline database of public exploits and vulnerability disclosures directly from your terminal.</p><p>Command : searchsploit UnrealIRCd</p><p><strong>Task 3 Answers:</strong></p><ul><li>linux/remote/13853.pl</li></ul><h3>Initial Access</h3><p>The good part about the exploit we are going to use is that there’s a Metasploit module for it. This makes exploitation much easier than modifying exploit scripts. Let’s fire up Metasploit first.</p><p>msfconsole</p><p>Follow the instructions in the room and you will be able to get the flag easily!</p><p><strong>Task 4 Answers:</strong></p><ul><li>THM{Pwned-Y0ur-First-Machine}</li></ul><h3>Post Exploitation</h3><p>Now that we’ve gotten a foothold on the target machine, we need to check for ways to escalate our privileges.</p><p>To find the flag in this room, we need to get the root password first. Which we found to be <strong>PDLrCVl1pLD91U0JMmCz</strong></p><p>Now ssh into root account: ssh root@TARGET_IP</p><p><strong>Task 5 Answers:</strong></p><ul><li>THM{Escalat1on-D0ne}</li></ul><h3>Reporting</h3><p>A good penetration test report must contain:</p><ul><li>A cover page with a title, your name, and email address, and version control.</li><li>A table of contents (Optional).</li><li>An executive summary, aimed at the manager who requested the engagement, explaining what was achieved in non-technical terms.</li><li>A technical summary aimed at the engineering manager, so they understand the impact and can prioritize accordingly (Optional).</li><li>A table of all vulnerabilities found, ordered by severity, aimed at managers and engineers, again to prioritize accordingly.</li><li>Detailed exploitation section, where each vulnerability and its impact are explained, exploitation steps and proof are shown, and recommendations for mitigations are given. This is aimed at engineers who will remediate your findings.</li></ul><p><strong>Task 6 Answers:</strong></p><ul><li>technical summary</li></ul><h3>Conclusion</h3><p>Hope this writeup helped you! Stay tuned for more room writeups.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4666bef4205f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Solving Room “Guided Pentest: Web” (TryHackMe)]]></title>
            <link>https://rad0v.medium.com/solving-room-guided-pentest-web-tryhackme-c916de38e0ce?source=rss-8c7153015c28------2</link>
            <guid isPermaLink="false">https://medium.com/p/c916de38e0ce</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[tryhackme-writeup]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[tryhackme]]></category>
            <dc:creator><![CDATA[rad0v]]></dc:creator>
            <pubDate>Thu, 21 May 2026 18:06:15 GMT</pubDate>
            <atom:updated>2026-05-21T18:06:15.261Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b7xIbghATi4sdYmSBOOA4A.png" /></figure><h3>Introduction</h3><p>In this walkthrough, I’ll be solving the <em>Guided Pentest: Web</em> room from TryHackMe. This room simulates a practical web application penetration test and walks through common stages of a web assessment, including reconnaissance, enumeration, vulnerability discovery, and exploitation.</p><p>Rather than blindly hunting for flags, the goal here is to understand the methodology behind web penetration testing and build a repeatable workflow.</p><p>Please note this is a not a walkthrough and is strictly for those who are stuck at finding the answers!</p><p>Room link: <a href="https://tryhackme.com/room/guidedpentestweb">https://tryhackme.com/room/guidedpentestweb</a></p><p><strong>Task 1: No answers needed!</strong></p><h3>Recon and Enumeration</h3><p>Before touching the application, let’s understand what we are working with. In any penetration test, the first phase is always reconnaissance; gathering as much information about the target as possible without making assumptions. You would never walk into a building you are hired to assess without first looking at the exterior, checking the doors, and reading the signs. The same principle applies here.</p><p><strong>Task 2 Answers:</strong></p><ol><li>2.4.58</li><li>MySQL</li><li>/reset.php</li></ol><h3>IDOR</h3><p>Now that we have an authenticated session and know the application’s structure, let’s start looking for vulnerabilities. One of the most common and frequently overlooked flaws in web applications is <strong>Insecure Direct Object Reference (IDOR)</strong>.</p><p>Consider this analogy: you are staying in a hotel, and your room key is simply your room number 104. There is no electronic lock, no verification, just the number. What stops you from walking to room 105 and opening the door? Nothing. That is essentially what an IDOR vulnerability is: the application uses a predictable identifier to reference objects (user profiles, documents, orders) and does not verify whether the requesting user is authorised to access that specific object.</p><p><strong>Task 3 Answers:</strong></p><ol><li>Sarah Mitchell</li><li>hiring_manager</li></ol><h3>Weak Password Reset</h3><p>We now know the administrator’s email address. Our next objective is to take over her account. Instead of trying to guess her password (which could take a long time and trigger account lockouts), let’s examine the password reset mechanism. Password reset flows are one of the most commonly broken features in web applications because they are complex to implement securely, and developers often take shortcuts.</p><p><strong>Task 4 Answers:</strong></p><ol><li>6</li><li>Administrator</li></ol><h3>Admin Panel Access</h3><p>We are now logged in as Sarah Mitchell, the application’s administrator. Earlier during our enumeration, Gobuster discovered an /admin path that redirected unauthenticated users to the login page. Now that we have administrator credentials, let&#39;s see what is behind that door.</p><p><strong>Task 5 Answers:</strong></p><ol><li>upload.php</li><li>accept</li><li>.phtml</li></ol><h3>Remote Code Execution</h3><p>We have confirmed that we can upload PHP files to the server and that the server will execute them. This is the point in the penetration test where all the previous steps come together. We started with nothing, no credentials, no knowledge of the application. Through enumeration, IDOR exploitation, password reset abuse, and admin panel access, we have reached a position where we can execute arbitrary code on the server.</p><p><strong>Task 6 Answers:</strong></p><ol><li>www-data</li><li>recruitx-prod</li><li>THM{ch41n3d_vulns_4r3_d3v4st4t1ng}</li></ol><h3>The Attack Chain</h3><p>Let’s take a step back and look at the full path we followed. In a penetration test report, you would document the entire chain of vulnerabilities, showing the client how each weakness contributed to the overall compromise. Here is our chain:</p><ol><li><strong>Enumeration</strong>: We discovered the application’s technology stack (Apache, PHP, MySQL), its directory structure, an API endpoint, a password reset page, an uploads directory, and an admin panel.</li><li><strong>IDOR (Task 3)</strong>: The /profile.php?id= parameter and the /api/user?id= endpoint allowed us to enumerate all users, including the administrator&#39;s name and email address.</li><li><strong>Weak Password Reset (Task 4)</strong>: The reset mechanism displayed tokens directly in the HTTP response, allowing us to generate a token for the administrator and change her password.</li><li><strong>Admin Panel Access (Task 5)</strong>: Using the compromised administrator account, we accessed the admin panel and found a file upload function with an incomplete extension blocklist.</li><li><strong>Remote Code Execution (Task 6)</strong>: We uploaded a PHP web shell using the .phtml extension, which bypassed the filter. This gave us command execution on the server and a path to a full reverse shell.</li></ol><p><strong>Task 7 Answers:</strong></p><ol><li>4</li><li>allowlist</li></ol><h3>Conclusion</h3><p>In this room, we walked through a complete web application penetration test, from the initial Nmap scan to remote code execution on the underlying server. Along the way, you practised the mindset that separates a good penetration tester from a great one: patience, observation, and the ability to connect findings across different parts of an application.</p><p><strong>Task 8: No Answers needed</strong></p><p>And with this the room is done!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c916de38e0ce" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>