The No-Nonsense Guide to Cybersecurity Vulnerabilities

dhanushnehru.medium.com · Dhanush N · 4 days ago · vulnerability
quality 7/10 · good
0 net
Tags
The No-Nonsense Guide to Cybersecurity Vulnerabilities | by Dhanush N - Freedium Milestone: 20GB Reached We’ve reached 20GB of stored data — thank you for helping us grow! Patreon Ko-fi Liberapay Close < Go to the original The No-Nonsense Guide to Cybersecurity Vulnerabilities From CVSS scores to Host Scanners, everything you need to understand your security posture before the bad guys do. Dhanush N Follow ~5 min read · April 6, 2026 (Updated: April 6, 2026) · Free: No Let's be honest for a second. Cybersecurity can feel like a maze of acronyms designed specifically to confuse people. CVE, CVSS, Host-Based Scanners, Misconfigurations… if you've ever looked at a security report and felt a headache coming on, you're not alone. But here is the harsh reality: if you don't understand your vulnerabilities, someone else will. And they probably won't be friendly. Whether you're a developer trying to secure your first app, an IT admin locking down a corporate network or just a tech enthusiast wanting to understand the hacker mindset, you need to know the fundamentals. Let's break down the core terminology of vulnerability scanning into plain English: no PhD in cryptography required. GitHub - DhanushNehru/Ultimate-Cybersecurity-Resources: A collection of cybersecurity resources for… A collection of cybersecurity resources for hackers, pentesters and security researchers … github.com Core Terminology: The Vocabulary of Breaches Before we talk about how to find the holes in your ship, we need to agree on what a "hole" actually is. 1. Vulnerability At its core, a vulnerability is simply a weakness or flaw in a system that could be exploited to bypass security or gain unauthorized access. It might be the result of using outdated software, poor configuration, or just plain old design mistakes. Think of it like this: It's a door with a broken lock. Anyone who jiggles the handle can open it, even though it's supposed to stay secure. 2. Common Vulnerabilities and Exposures (CVE) A CVE is a unique identification number (e.g., CVE-2026–12345) assigned to a publicly known security flaw. This universal ID system allows security teams, vendors, and hackers to all talk about the exact same issue without confusion. Think of it like this: It's similar to a product recall number for a faulty car part, but applied to software vulnerabilities. 3. Common Vulnerability Scoring System (CVSS) Not all vulnerabilities are created equal. CVSS provides a standardized score from 0 to 10 that measures the severity or risk of a vulnerability based on its impact and how easy it is to exploit. A 9.8 is a "drop everything and fix this now" problem, while a 3.2 might wait until the next patch cycle. Think of it like this: It's much like weather alerts. A CVSS 2 is a light drizzle; a CVSS 10 is a Category 5 hurricane heading straight for your data center. 4. Misconfiguration A misconfiguration occurs when a system or service is set up incorrectly, creating entirely unnecessary security weaknesses. These issues almost always arise from human error: default settings left unchanged, excessively open permissions, or a lack of basic hardening. Think of it like this: Leaving a Wi-Fi network protected with a password like "123456", or putting your spare house key under the doormat that says "Welcome." 5. Software Vulnerability A software vulnerability is a specific flaw in an application's code or logic that allows unintended behavior or exploitation. These weaknesses often require developers to rewrite code or release patches to fix the root cause. Think of it like this: A calculator app that crashes or worse, gives you system administrator access, just because you tried to divide by zero in a specific way. The Threat Hunter's Toolkit: Types of Vulnerability Scanners Now that we know what we're looking for, how do we find it? We use automated vulnerability scanners. But you can't just use one scanner for everything. You need the right tool for the right job. 1. The Network Scanner A network scanner roams your digital perimeter. It examines devices across a network to identify open ports, running services, and possible exposure points. It helps map out what systems are accessible from the outside and where risks might exist. 🕵️‍♂️ The Analogy: It's like walking down your street and checking which doors or windows are unlocked on every house. 2. The Web Application Scanner A web application scanner is highly specialized. It analyzes websites or web apps specifically for HTTP/HTTPS layer security issues, including outdated components, weak configurations, or risky behaviors like SQL injection flaws. 🕵️‍♂️ The Analogy: It's like testing a login form to see if it accepts weird inputs, or trying to trick a bouncer into letting you into a club using a fake ID. 3. The Host-Based Scanner A host-based scanner gets up close and personal. It runs directly locally on a single system (like a specific server or laptop) to check for missing patches, outdated software, and insecure configuration settings. It provides a highly detailed, intimate view of internal system health. 🕵️‍♂️ The Analogy: Similar to a doctor giving you an MRI to check your internal organs, rather than just looking at you from across the room. Decoding the Output: Reading a Scanning Report So, you ran your scanners and it spit out a massive PDF. Now what? A reliable, professional vulnerability scanning report should always include these four critical components: The Severity Level: Usually color-coded (Critical, High, Medium, Low), indicating exactly how serious the issue is and what to prioritize. Detected Services & Versions: Information on exactly what software triggered the alert (e.g., "Apache 2.4.49"). Related CVEs: The exact identification numbers so your team can read the public documentation on the known risks. Recommended Fixes or Mitigation Steps: Actionable advice. A good report doesn't just tell you that your house is on fire — it hands you the fire extinguisher. The Takeaway Vulnerability scanning isn't a one-and-done task; it's a continuous hygiene practice. The internet changes every single day, and the secure configuration you deployed last month might be severely vulnerable tomorrow morning. Stop guessing about your security posture. Learn the terminology, pick the right scanners for your infrastructure, and start finding those broken locks before someone else does. (If you found this guide helpful, don't forget to share it with your dev team or anyone looking to level up their cybersecurity knowledge!) Who Am I ? Hi, I'm Dhanush Nehru an Engineer, Cybersecurity Enthusiast, Youtuber and Content creator. I document my journey through articles and videos, sharing real-world insights about DevOps, automation, security, cloud engineering and more. You can support me / sponsor me or follow my work via X , Instagram , Github or Youtube #cybersecurity #cyber-security-awareness #information-security #security #bug-bounty Reporting a Problem Sometimes we have problems displaying some Medium posts. If you have a problem that some images aren't loading - try using VPN. Probably you have problem with access to Medium CDN (or fucking Cloudflare's bot detection algorithms are blocking you).