<?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"><channel><title><![CDATA[xSecurity]]></title><description><![CDATA[xSecurity]]></description><link>https://0xsec.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Thu, 12 Nov 2026 07:29:17 GMT</lastBuildDate><atom:link href="https://0xsec.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Day 1 of my learning:]]></title><description><![CDATA[My Day 1 learning covering BAC (Vertical/Horizontal), IDOR, session state, modern Linux File Systems (Inodes, Links, VFS) from standard sources.]]></description><link>https://0xsec.hashnode.dev/day-1-my-learning-broken-access-control-linux-file-system</link><guid isPermaLink="true">https://0xsec.hashnode.dev/day-1-my-learning-broken-access-control-linux-file-system</guid><category><![CDATA[cybersecurity]]></category><category><![CDATA[#infosec]]></category><category><![CDATA[bugbounty]]></category><category><![CDATA[Linux]]></category><category><![CDATA[Web Security]]></category><category><![CDATA[#learning-in-public]]></category><dc:creator><![CDATA[Ethical Hacker]]></dc:creator><pubDate>Wed, 11 Nov 2026 18:28:13 GMT</pubDate><content:encoded><![CDATA[<p>Today I learned about broken access control and modern Linux file systems. Below is the breakdown of my core technical learning and practical takeaways for today:</p>
<ol>
<li>Web Security: Authentication, Authorization &amp; Access Control Core Concepts: Explored how HTTP is a stateless protocol, relying on authentication, authorization, and session tokens to manage user identity and access states.</li>
</ol>
<p><strong>Broken Access Control:</strong> Studied the core concept of access control failures, which PortSwigger and OWASP categorize into three main types:</p>
<p><strong>Vertical Access Control Failures:</strong> Accessing privileged functionality (or resources) that should be restricted to specific user roles.</p>
<p><strong>Horizontal Access Control Failures:</strong> Accessing resources belonging to other users with the same privilege level (noting that Insecure Direct Object References / IDOR are a specific manifestation of horizontal access control failure).</p>
<p><strong>Context-Dependent Access Control Failures:</strong> Accessing functions out of sequence or violating application workflow constraints.</p>
<p>Root Causes of Access Control Vulnerabilities: Identified six common developer mistakes:</p>
<ol>
<li>Relying solely on removing UI buttons/elements from the front-end while assuming the back-end is safe.</li>
<li>Trusting the user's login session rather than verifying object ownership.</li>
<li>Failing to check every HTTP method.</li>
<li>Failing to check every API route.</li>
<li>Relying on previous permission states (e.g., assuming a user who completed Stage 1 remains authorized for Stage 3 without re-validation).</li>
<li>Relying on "guessable" or predictable IDs as a form of security.</li>
</ol>
<p>ID Types: Examined predictable versus unpredictable identifiers used within applications.</p>
<p>Hands-On Practice: Successfully solved the "<strong>Unprotected admin functionality</strong>" lab on PortSwigger Web Security Academy, reinforcing how missing server-side authorization allows unauthenticated users to access admin paths and execute privileged actions (such as deleting a user).</p>
<ol start="2">
<li><strong>Operating Systems: Modern Linux File Systems Studied core operating system architecture from the book Learning Modern Linux (2022) by Michael Hausenblas, specifically focusing on Chapter 5 (File Systems):</strong></li>
</ol>
<p>File System Hierarchy: File systems start at the root directory denoted by a slash (/), containing directories and files.</p>
<p>Nodes &amp; Leaves: Directories act as nodes, while files and directories act as leaves in the system structure.</p>
<p><strong>Storage Units:</strong></p>
<p><strong>HDD / SSD:</strong> The physical hardware storage devices.</p>
<p><strong>Partitioning:</strong> Dividing a physical hard disk drive into separate, independent parts.</p>
<p><strong>Volumes:</strong> Function similarly to partitions but offer greater flexibility, typically used for special file system formatting.</p>
<p><strong>Superblock:</strong> Records critical structural information about the file system itself.</p>
<p><strong>Inodes:</strong> Store the metadata associated with files in the file system.</p>
<p><strong>Links:</strong> Mechanisms to access the same file using alternative names or shortcuts:</p>
<p>Hardware Links: Accessing the same file through a direct hardware link/alternative name.</p>
<p>Symbolic Links: Acting as a shortcut to point to a target file path.</p>
<p>VFS &amp; Core Abstractions: Explored the Virtual File System (VFS) abstraction layer, along with temporary file systems (tmpfs), process file systems (procfs), network file systems (nfs), drivers, inodes, dentries, and mount points.</p>
]]></content:encoded></item></channel></rss>