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

41. Session Hijacking – Tokens, Cookies and Defence

41.6 Application-Level Hijack – URL Tokens, CSRF, JWT Concepts

By Last updated:

Not every hijack is Wi-Fi sniff:

  • Session ID in URL (?PHPSESSID=...) – leaks via Referer, logs, screenshots, shoulder surfing
  • CSRF vs session: CSRF = browser already has victim cookie; attacker tricks browser to send request. Different from stealing cookie – but related session hygiene (SameSite, CSRF tokens)
  • JWT pitfalls (concept level): token in localStorage → XSS readable; none / weak alg; long expiry; no revoke list; secrets in client

Blue habits:

  • Prefer cookie session with HttpOnly over URL SID
  • CSRF token on state-changing POSTs; SameSite=Lax/Strict
  • JWT: short TTL, secure storage choices, validate alg/iss/aud, rotate secrets server-side
Red team (attacker) does Blue team (defender) detects / stops
Copies SID from URL bar / proxy log Cookie-based SID; regenerate; no SID in GET
CSRF on "transfer / change email" while session valid CSRF token + SameSite; re-auth for sensitive ops
Abuses fat JWT in localStorage via XSS Prefer HttpOnly cookie patterns where fit; CSP; short JWT TTL

Ravindra Bagale's Tip

Students think JWT = "modern, so automatically safe". JWT is a format; safety depends on how you sign, store, expire and validate it. In interviews, name 3 pitfalls. Remember this.

Practice task

Raja-Rani Traders wants "remember me for 30 days" JWT in localStorage. Write 10-line risk memo for owner Raja: XSS, theft, revoke difficulty. Propose safer pattern (short access + refresh, HttpOnly cookie, or server session). No production deploy without HTTPS.

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.