Penetration › Module 5 › Lesson 2
Read Before Run
Read advisories and PoC notes fully — assess applicability on $LAB_HOST before any lab validation attempt.
Visual · pentest_read_before_run
Read before run literacy. $LAB_HOST only. Original Cyberlium.
Opening
Running unread exploits is how students break labs and laws.
Before any lab validation, pentesters read: affected versions, prerequisites, side effects, and authentication requirements. Applicability checks ask: does $LAB_HOST actually run the vulnerable build? Is the service configured as the advisory assumes? Would validation violate RoE destructiveness limits? Cyberlium never provides step-by-step weaponized exploit walkthroughs against strangers. You read advisories on scoped findings and plan lab-only validation — or document 'not applicable' with evidence. Next: Lab-Only Exploit.
1. Applicability checklist
Version exact match or within affected range? Patch backported? Service exposed on $LAB_HOST as advisory expects? Authentication required? Lab snapshot taken?
If any check fails, mark finding 'not applicable' in notes — do not force exploit for trophy.
Command guide
Try these commands — Applicability checklist
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
SearchSploit -w — https://www.exploit-db.com/searchsploit Exploit review — lab VM versions only
═══ INSTALL ═══
Linux (Debian/Ubuntu):
Command — copy this
sudo apt install exploitdb
macOS: Prefer Kali: searchsploit
Windows: Use Kali VM — searchsploit from exploitdb
═══ LINUX / macOS ═══
Command — copy this
searchsploit -w openssh | head -15 searchsploit --id 12345 2>/dev/null || searchsploit linux kernel | head -10
Primary tools to practice this lesson: searchsploit. Reference sites: SearchSploit -w (https://www.exploit-db.com/searchsploit); Exploit review. Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Read for impact and scope fit
Advisories describe confidentiality, integrity, availability impact. RoE may forbid destructive chains even on $LAB_HOST. Read side effects: crash risks, data wipe, lateral modules.
Unread copy-paste from forums onto classmate machines is unauthorized access — not literacy.
3. Document the read — not just the run
Notes include: advisory URL/title, applicability result, planned lab validation or skip reason. Reports cite reading — strangers never enter this chain.
Ship: applicability checklist block for $LAB_HOST findings. Next: Lab-Only Exploit.
4. What you ship: applicability checklist for advisories
Checklist: version, patch, exposure, auth, snapshot, RoE fit. $LAB_HOST only. chmod 600.
5. What you record before the next lesson
Date. Applicability checklist. $LAB_HOST reference. File t19-m05-l02-read-before-run.txt chmod 600.
6. Wrong vs right: stranger nets vs YOUR lab VMs
Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.
Wrong
Skip reading and run first Exploit-DB match on dorm host. Ignore backported patch on $LAB_HOST.
Right
Write applicability checklist for advisory reading. Next: Lab-Only Exploit.
Mission: freeze read-before-run checklist
1) List six applicability checks. 2) Tie to $LAB_HOST enumeration finding. 3) chmod 600. Never run unread exploits on strangers.
Stuck? Ask Cyberlium AI Mentor
Most 'failed' exploits are applicability failures — read first.
Knowledge Check
APPLY: Before lab validation on $LAB_HOST you should:
Multiple choice
Knowledge Check
APPLY: True or False: Backported patches can make CVE appear non-applicable.
True or False
Knowledge Check
APPLY: If applicability fails on $LAB_HOST, you:
Multiple choice