GHOSTNET›MOD-03›MOD-04 // OFFENSIVE SECURITY
MOD-05 ›
MODULE 04 · OFFENSIVE SECURITY

OFFENSIVE SECURITY

Vulnerability research · Exploitation fundamentals · Stack overflows · Modern mitigations · ROP · Heap exploitation · Web/network exploits · Fuzzing

8
CHAPTERS
~2.8hr
TOTAL READ
INTERMEDIATE
DIFFICULTY
MOD-04
IDENTIFIER
BEGINNER~18 min READCHAPTER 1 OF 8

Vulnerability Research Methodology

KEY POINTS · THE QUICK VERSION
  • CVSS v3.1 scores vulnerabilities 0-10 across Base, Temporal, and Environmental metric groups.
  • CVE identifies specific vulnerabilities; CWE classifies the underlying weakness type.
  • Responsible disclosure gives vendors time to patch before public details are released.
  • Bug bounty platforms (HackerOne, Bugcrowd, Intigriti) let researchers earn rewards legally.
  • Patch diffing reveals exactly what a vendor fixed, which often points directly to the vulnerability.
Scan these first, then read below for the depth and examples — or jump straight to the lab.
BEGINNER NOTE
Vulnerability research is the systematic process of finding security flaws before attackers do - or understanding flaws after they are discovered. Every exploit starts with a vulnerability, so understanding how they are classified and tracked is essential context for everything else in this module.

The security industry uses standardised systems to track, score, and communicate vulnerabilities. These systems let defenders prioritise what to patch first and let researchers publish findings in a structured way.

◈ PICTURE IT — MTAANI EDITION

Walk into Naivas looking for cooking oil. "Cooking oil" is a whole shelf category — that is a CWE, the kind of weakness. But the 2-litre Elianto bottle with batch number 4471 sitting on that shelf is one exact product — that is a CVE, this specific flaw in this specific software. The shop tracks both the category and the exact item on the shelf, and so do security researchers.

► CVE and CWE - The Classification Systems

A CVE (Common Vulnerabilities and Exposures) is a specific instance of a vulnerability in a specific product. A CWE (Common Weakness Enumeration) is the category of weakness that caused it. The distinction matters: CWE-79 is "Cross-site Scripting" (the weakness type); CVE-2021-44228 is Log4Shell (the specific instance in Log4j).

TERMWHAT IT ISEXAMPLE
CVEUnique ID for a specific vulnerability in a specific productCVE-2021-44228 (Log4Shell in Log4j)
CWECategory of weakness that leads to vulnerabilitiesCWE-79 XSS, CWE-89 SQLi, CWE-119 Buffer Overflow
NVDNIST National Vulnerability Database - enriches CVEs with CVSS scoresnvd.nist.gov
MITREMaintains the CVE list and CWE listcve.mitre.org, cwe.mitre.org
Exploit-DBPublic exploit archive, searchable by CVE or productexploit-db.com
Rapid7 VulnDBCommercial vuln database with deep technical detailvulndb.rapid7.com

► CVSS Scoring - How Severity is Measured

CVSS (Common Vulnerability Scoring System) produces a 0.0-10.0 score. Version 3.1 is current; version 4.0 was released in 2023. The score has three metric groups:

GROUPMETRICSWHAT IT MEASURES
BaseAttack Vector, Attack Complexity, Privileges Required, User Interaction, Scope, Confidentiality/Integrity/Availability ImpactIntrinsic severity of the flaw itself, unchanged by time or environment
TemporalExploit Code Maturity, Remediation Level, Report ConfidenceHow the severity changes over time (PoC available? Patch released?)
EnvironmentalModified Base metrics + Confidentiality/Integrity/Availability RequirementsSeverity adjusted for YOUR specific environment and asset criticality
CVSS RANGESEVERITYTYPICAL MEANING
0.1 - 3.9LOWDifficult to exploit, minimal impact
4.0 - 6.9MEDIUMSome exploitation difficulty or limited impact
7.0 - 8.9HIGHRelatively easy to exploit with significant impact
9.0 - 10.0CRITICALNetwork-exploitable, no auth, full system compromise possible
WARNING
CVSS scores describe severity, not risk. A CVSS 10.0 on an internet-isolated system may be less urgent than a CVSS 7.0 on your public web server. Always apply environmental context.

► Vulnerability Lifecycle

Understanding where a vulnerability sits in its lifecycle determines how urgent patching is and what exploit options exist:

VULNERABILITY LIFECYCLE
DISCOVERY       Researcher or attacker finds the flaw
     |
     v
PROOF OF CONCEPT  Minimal code confirming exploitability (PoC)
     |
     v
WEAPONISATION   PoC refined into reliable exploit (may include evasion)
     |
     v
PATCH RELEASE   Vendor releases fix
     |
     v
N-DAY WINDOW    Vulnerable systems still unpatched - race against time
     |
     v
PATCH COMPLETE  Exposure minimised (never zero - some never patch)

► Zero-Day vs N-Day

A zero-day (0-day) is a vulnerability that has no available patch - "zero days" for defenders to patch before attackers exploit it. An N-day is a vulnerability with a patch available for N days. N-days are often more dangerous in practice because they are well-documented and widely weaponised, but many organisations patch slowly.

► Disclosure Models

MODELAPPROACHPROSCONS
Responsible/CoordinatedResearcher notifies vendor privately, gives fix deadline (typically 90 days per Google Project Zero), then publishesGives vendors time to patch; industry standardVendors may drag feet; stressful for researcher
Full DisclosureResearcher publishes all details immediately with no vendor notificationForces vendors to act; helps defenders tooGives attackers immediate weaponisable details
Bug Bounty (HackerOne, Bugcrowd, Intigriti)Researcher submits via platform, receives monetary reward per programme scopeLegal, paid, structured, often includes coordinated disclosureProgramme scope limits what you can test; triage delays

► Patch Diffing

When a vendor releases a security patch, the difference between the patched and unpatched binary reveals exactly what was fixed. Tools like BinDiff (Zynamics/Google) and Diaphora (open source) perform binary diffing to identify changed functions. Researchers use this to reconstruct the vulnerability from the patch - often faster than independent discovery.

PATCH DIFFING WORKFLOW
1. Download vulnerable version binary
2. Apply vendor patch to get patched binary
3. Load both into BinDiff/Diaphora
4. Identify changed functions (highlighted by diff tool)
5. Analyse changed function in Ghidra/IDA to understand the fix
6. Work backwards to understand the exploitable path in the old version
RECAP · CHECK YOURSELF
  • CVSS v3.1 scores vulnerabilities 0-10 across Base, Temporal, and Environmental metric groups.
  • CVE identifies specific vulnerabilities; CWE classifies the underlying weakness type.
  • Responsible disclosure gives vendors time to patch before public details are released.
  • Bug bounty platforms (HackerOne, Bugcrowd, Intigriti) let researchers earn rewards legally.
  • Patch diffing reveals exactly what a vendor fixed, which often points directly to the vulnerability.
Read to the end to count this chapter
▸ READY TO PRACTISE
You've now covered enough for Lab steps 1–2 of 20. Try them in the lab while it's fresh.
OPEN LAB ▸
⚡ TEST YOURSELF
End-of-chapter quiz
A dozen questions — recall and practical. Graded, earns up to 20 XP.
PRACTISE IN THE LAB ▸
READY TO PRACTICE?
MOD-04 Interactive Lab
20 steps · 400 XP · Real commands · Flag captures
LAUNCH LAB →
← MOD-03: CRYPTOMOD-05: ACTIVE DIRECTORY →