Ravindra BagaleCourses & study guides मराठी Track your progress

48. CEH v13 Exam Modules Map and Practice Questions

48.4 Modules 11–15 Map (Session Hijacking through SQL Injection)

By Last updated:

Web-heavy cluster. OWASP + sessions + SQLi. He cluster CEH + job donhi madhe weighty.

Module 11 – Session Hijacking
Book: ch41 (Session Hijacking – Tokens, Cookies and Defence).
Focus: cookie/token theft ideas on clear HTTP; fixation themes at awareness level.
Blue: HTTPS, Secure/HttpOnly/SameSite, regenerate session ID at login, short idle timeout.

Module 12 – Evading IDS, Firewalls, and Honeypots
Book: ch42 (Evading IDS, Firewalls and Honeypots), ch32 (Linux and Network Hardening).
Focus: why attackers fragment/encode/slow-scan in concept; defenders still win with layers.
Blue: IDS/IPS tuning, egress filter, honeypot isolation, Suricata-style awareness, least open ports.

Module 13 – Hacking Web Servers
Book: ch07, ch08 (Apache/Nginx install and config), ch21 (Web Application Testing Tools).
Focus: misconfig, default pages, verbose errors, outdated server banners – OWN stack.
Blue: patch httpd/nginx, hide versions where sensible, tight file perms, sudo service httpd restart after tested config.

Module 14 – Hacking Web Applications
Book: ch21, ch29 (OWASP Top 10).
Focus: XSS, broken access control/IDOR, SSRF, security misconfig – fix then re-verify on DVWA/Juice OWN.
Blue: output encoding + CSP, authZ checks, allow-lists, disable debug, secrets out of repos.

Module 15 – SQL Injection
Book: ch10, ch11 (MySQL), ch29 (OWASP SQLi class).
Focus: why string-concat SQL is dangerous; prepared statements as the fix; lab proof only.
Blue: parameterised queries, least-privilege DB user, WAF as layer (not only layer), error messages generic.

Red team (attacker) does Blue team (defender) detects / stops
Steals session cookie on clear HTTP lab demo HTTPS + cookie flags; session regenerate on login
Explains SQLi on OWN DVWA order field PDO/mysqli prepared statements; re-test until old OR-style input fails
Noise against public IDS "to practise evasion" Only OWN lab; production = report + improve rules

Ravindra Bagale's Tip

In Module 15 answers, don't paste a real OR payload, not even on an exam cheat-sheet – keep it conceptual: "a quoted OR condition that changes the WHERE clause". The interviewer looks at the fix. Got it?

Lab

Sahyadri OWN 192.168.56.50 PHP lookup: break it with concat SQL (lab), then fix with prepared statements. From Kali prove the old input no longer returns all rows. Screenshot weak → fixed for Module 15 revision.

Extended teaching notes

Why this lesson matters

Web flaws stay in the OWASP Top 10 because real apps still ship them. Your job is not to collect tool screenshots. It is to prevent and fix the class of bug on systems you own.

Apply the fix across stacks

Same class of bug, same idea in every language.

Java / Spring Boot

Parameterise queries, encode output, CSRF tokens, limited Actuator, dependency scanning.

ASP.NET Core

EF Core / parameterised SQL, Razor encoding, HTTPS, Data Protection.

Node.js / Express

helmet, parameterised SQL, npm audit, avoid eval and shell concat.

Python / Django / Flask / FastAPI

ORM, autoescape, pip-audit, Bandit; never shell=True with user input.

PHP / Laravel

PDO/Eloquent, Blade escaping, composer audit.

Go / Ruby

database/sql placeholders / ActiveRecord; html/template / ERB escaping; govulncheck / Brakeman.

nginx / Apache / Tomcat

Hide versions, TLS, security headers, least-open ports.

MySQL / PostgreSQL / MongoDB / Redis

Private networks, auth on, least-privilege users, no 0.0.0.0/0.

AWS / Azure / GCP

Roles not long-lived keys, private data stores, cloud audit logs on.

Real examples

Global: injection and XSS still appear in breach reports and bug bounties every year. Indian company (sample): a Bengaluru SaaS team maps each OWASP item to a CI check or a code-review question so new code cannot silently reintroduce it.

Mini case study

Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.

Defender's worksheet (do this today)

  1. Write the lesson title, date and the exact lab target you are allowed to use.
  2. List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
  3. Run one safe check from the lesson on a lab system only. Paste the command and output.
  4. Write a two-sentence fix you would give a teammate.
  5. Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.

Indian workplace (sample data)

Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).

Global practice

Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.

Everyday analogy

Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.

Key terms

  • Control: a safeguard (patch, config, process, detection).
  • Finding: a weakness backed by evidence.
  • Remediation: the fix plus how you verified it.
  • Scope: systems you have written permission to touch.
  • Least privilege: only the access the task needs.
  • Defence in depth: several layers so one failure does not end the story.

Common mistakes

  • Skipping written permission "just for a quick scan".
  • Practising on hostel, office or public targets without authorisation.
  • Collecting tool output without writing the fix.
  • Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
  • Publishing screenshots that contain secrets, cookies or internal hostnames.

Recap

  • Evidence, fix, owner, date.
  • Own lab only.
  • Fix > spectacle.