Log Poisoning Techniques

Overview

Log poisoning combines LFI with log file contamination to achieve remote code execution by injecting malicious code into log files that can later be included and executed.

Prerequisites:

  • LFI vulnerability allowing access to log files

  • Ability to control logged data (User-Agent, HTTP headers, SSH attempts, etc.)

  • Web server with write permissions to log files


Method 1: PHP Session Poisoning

Complete 5-Step Workflow

Step 1: Identify Session File Location

# Common PHP session locations
/var/lib/php/sessions/sess_PHPSESSID
/tmp/sess_PHPSESSID

# Get PHPSESSID from cookies
curl -I http://target.com/ | grep -i set-cookie

Step 2: Poison Session Data

Step 3: Execute Commands


Method 2: Apache/Nginx Access Log Poisoning

User-Agent Poisoning

Step 1: Identify Log Location

Step 2: Poison User-Agent Header

Step 3: Execute via Log Inclusion


Method 3: SSH Log Poisoning

SSH Auth Log Contamination

Step 1: Identify SSH Log Location

Step 2: Poison SSH Login Attempts

Step 3: Execute via Log Inclusion


Method 4: Mail Log Poisoning

SMTP Log Contamination

Common Mail Logs:

Poisoning Technique:


Method 5: FTP Log Poisoning

FTP Authentication Logs

Log Locations:

Poisoning via FTP Login:


HTB Academy Log Poisoning Lab

Complete Lab Walkthrough

Objective: Achieve RCE via log poisoning and read flag

Step 1: Identify Vulnerable Parameter

Step 2: Test LFI

Step 3: Identify Session Location

Step 4: Poison Session

Step 5: Execute Commands


Advanced Log Poisoning Techniques

Multi-Field Poisoning

Persistent Shell Creation


[Content continues with troubleshooting and additional techniques...]

This guide covers advanced log poisoning techniques from HTB Academy's File Inclusion module.

Last updated