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

41. Session Hijacking – Tokens, Cookies and Defence

41.4 XSS Path to Session Cookies – Defence First

By Last updated:

XSS (Cross-Site Scripting) = attacker script runs in victim's browser in your origin. If session cookie is not HttpOnly, script can often read it and send it out. Even with HttpOnly, XSS can still act as the user (drive UI, CSRF-like actions) – so XSS fix is still mandatory.

High-level Blue (OWASP themes – no exploit kit here):

  • Output encoding / context-aware escaping
  • CSP (Content-Security-Policy) to limit script sources
  • HttpOnly on session cookies
  • Avoid innerHTML with raw user input; sanitize where needed
  • WAF as belt; code fix as suspenders
Red team (attacker) does Blue team (defender) detects / stops
Injects script into reflected/stored field on OWN lab app Encode output; CSP; input validation
Reads document.cookie when HttpOnly missing HttpOnly session cookie; short TTL
Uses XSS to call APIs as victim without stealing cookie CSP + SameSite + CSRF tokens + least privilege

Ravindra Bagale's Tip

Students say "HttpOnly = XSS is dead". HttpOnly reduces cookie theft – but XSS can still abuse the account. Fix the XSS + cookie flags + CSP. If this isn't clear, read it again.

Lab

OWN DVWA / Juice Shop / tiny PHP reflection page on host-only only. Show (trainer path) how a reflected field echoes script; note cookie visibility in DevTools with/without HttpOnly. Do not point at internet sites. Write 8-line fix note: encode, CSP header, HttpOnly, SameSite.

Real incident: British Airways Magecart-style skimming (2018)

In 2018, British Airways reported a supply-chain / malicious JavaScript injection on payment-related pages (Magecart-class public reporting) that harvested customer payment and personal data as users checked out. The UK ICO later issued a large fine under GDPR (widely reported; amounts and final figures – verify official ICO notices). Lesson for session/payment pages: third-party / injected JS on sensitive flows can steal secrets and session-adjacent data; CSP, subresource integrity, tight change control, and monitoring of payment page scripts matter. Source: BA / ICO public statements and major news coverage of the 2018 incident (verify; say "reported").

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.