DLL hijacking

5 minutes 5 Questions

DLL hijacking is a critical exploitation technique covered in the CompTIA PenTest+ curriculum, specifically falling under the "Attacks and Exploits" domain. It leverages the specific search order Microsoft Windows uses to locate and load Dynamic Link Libraries (DLLs). A DLL is a shared library containing code and data used by multiple programs. When an executable requests a DLL without specifying an absolute path, Windows searches for the file in a pre-defined sequence: typically starting with the application's current directory, followed by system directories (System32), the Windows directory, the current working directory, and finally, the directories listed in the system's PATH environment variable. The vulnerability exists when an application attempts to load a legitimate DLL that is missing from the application's directory or when the search order can be manipulated. An attacker exploits this by placing a malicious DLL with the exact name of the legitimate library (e.g., "user32.dll" or a proprietary library name) into a directory that Windows searches *before* locating the real file. When the application runs, it unknowingly loads the attacker's malicious code. In penetration testing, this vector is primarily used for privilege escalation and persistence. If the vulnerable application runs with administrative or SYSTEM privileges, the malicious DLL inherits those elevated permissions, granting the attacker full control over the host. Pen testers utilize tools like Process Monitor (Procmon) to identify "NAME NOT FOUND" errors—indicating an application is searching for a missing DLL—and then craft payloads using tools like Metasploit msfvenom. Mitigation requires developers to use absolute paths for loading libraries and administrators to enforce Safe DLL Search Mode to restrict the search order.

Deep Dive: DLL Hijacking for CompTIA PenTest+

What is DLL Hijacking?
Dynamic Link Library (DLL) Hijacking is a method used by attackers to force a legitimate application to load a malicious DLL instead of the intended, legitimate one. In Windows environments, applications rely on shared libraries (.dll files) to function. If an application does not specify the full path to a DLL, Windows follows a specific search order to locate it. By placing a malicious DLL in a directory that is searched before the directory containing the legitimate DLL, an attacker can execute arbitrary code.

Why is it Important?
This technique is a cornerstone concept for the CompTIA PenTest+ exam because it is a common method for both Privilege Escalation and Persistence. If a user runs a vulnerable application as an Administrator, the hijacked DLL will also run with Administrator privileges. It allows attackers to hide inside trusted processes, potentially bypassing allow-listing software.

How it Works: The Search Order
The vulnerability stems from the way Windows looks for files. When an application requests a DLL (e.g., library.dll) without a full path, Windows generally searches in this order (with SafeDllSearchMode enabled):
1. The directory from which the application loaded.
2. The system directory (C:\Windows\System32).
3. The 16-bit system directory.
4. The Windows directory.
5. The current directory.
6. Directories listed in the PATH environment variable.

The Attack Path:
1. Identification: The attacker uses tools like Process Monitor (Procmon) to look for applications attempting to load DLLs that result in a NAME NOT FOUND error, or applications loading DLLs from directories where the attacker has write access.
2. Creation: The attacker compiles a malicious DLL (often using msfvenom) with the same filename as the missing or targeted DLL.
3. Placement: The attacker places this file in a directory higher up in the search order (often the application's local directory).
4. Execution: When the application is launched (by a user or a service), it loads the malicious DLL, executing the payload.

Exam Tips: Answering Questions on DLL Hijacking
When facing questions on this topic, keep the following strategies in mind:

1. Recognize the Scenario:
If a question describes an attacker identifying a "missing DLL" using Procmon or mentions "NAME NOT FOUND," the answer is almost certainly related to DLL Hijacking.

2. Privilege Escalation vs. Persistence:
Determine the attacker's goal. If they replace a DLL used by a scheduled task or a service starting at boot, it is for Persistence. If they target an application run by an Administrator while they are a low-level user, it is for Privilege Escalation.

3. Remediation:
If asked how to fix this vulnerability, look for answers involving hardcoding absolute paths for DLLs in the application code or verifying file integrity (hashing).

4. Key Tools:
Associate Sysinternals Process Monitor (Procmon) with the detection of DLL hijacking vulnerabilities.
Test mode:
More DLL hijacking questions
30 questions (total)

Other Attacks and Exploits concepts

Adversarial machine learningAI data poisoningAI system attack vectorsAPI authentication attacksAPI security testingARP spoofing and poisoningAS-REP roastingAuthentication bypass techniquesAWS security testingAzure security testingBloodHound for ADBluetooth attacksBrute-force attacksCloud penetration testingCobalt Strike basicsCommand injectionContainer escape attacksCookie manipulationCredential dumpingCredential stuffingCross-site request forgery (CSRF)Cross-site scripting (XSS)Directory traversal attacksDNS poisoning attacksEmbedded device attacksEmpire frameworkFile inclusion vulnerabilitiesFirmware analysisGolden ticket attacksGraphQL security issuesHardware hacking basicsHashcat password crackingHydra password crackingIAM misconfiguration exploitationImpacket toolkitInsecure deserializationIoT penetration testingJohn the RipperKerberoastingKubernetes security attacksLinux privilege escalationLiving off the land binaries (LOLBins)LLMNR/NBT-NS poisoningMetadata service attacksMetasploit frameworkMimikatz usageModel manipulation attacksNetwork protocol attacksNTLM relay attacksOn-path attacks (MITM)Pass-the-hash attacksPass-the-ticket attacksPassword sprayingPrivilege escalation techniquesProcess injectionPrompt injection attacksRate limiting bypassResponder toolREST API vulnerabilitiesS3 bucket misconfigurationServerless function attacksServer-side request forgery (SSRF)Service exploitationSession hijackingSilver ticket attacksSQL injection attacksSQLmap usageToken manipulationUAC bypass techniquesVLAN hopping attacksWindows privilege escalationWireless network attacksXML external entity (XXE) attacks