Skip to content

Use DLL instead of Dll in section headings #2841

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
carlospolop merged 1 commit into from
Sep 19, 2026
+6 −6
Merged

Use DLL instead of Dll in section headings #2841

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/SUMMARY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -330,10 +330,10 @@
- [AppendData/AddSubdirectory permission over service registry](windows-hardening/windows-local-privilege-escalation/appenddata-addsubdirectory-permission-over-service-registry.md)
- [Create MSI with WIX](windows-hardening/windows-local-privilege-escalation/create-msi-with-wix.md)
- [COM Hijacking](windows-hardening/windows-local-privilege-escalation/com-hijacking.md)
- [Dll Hijacking](windows-hardening/windows-local-privilege-escalation/dll-hijacking/README.md)
- [Advanced Html Staged Dll Sideloading](windows-hardening/windows-local-privilege-escalation/dll-hijacking/advanced-html-staged-dll-sideloading.md)
- [DLL Hijacking](windows-hardening/windows-local-privilege-escalation/dll-hijacking/README.md)
- [Advanced Html Staged DLL Sideloading](windows-hardening/windows-local-privilege-escalation/dll-hijacking/advanced-html-staged-dll-sideloading.md)
- [Windows CPython Build-Landmark and sys.path Hijacking](windows-hardening/windows-local-privilege-escalation/dll-hijacking/windows-cpython-build-landmark-sys-path-hijacking.md)
- [Writable Sys Path +Dll Hijacking Privesc](windows-hardening/windows-local-privilege-escalation/dll-hijacking/writable-sys-path-dll-hijacking-privesc.md)
- [Writable Sys Path +DLL Hijacking Privesc](windows-hardening/windows-local-privilege-escalation/dll-hijacking/writable-sys-path-dll-hijacking-privesc.md)
- [DPAPI - Extracting Passwords](windows-hardening/windows-local-privilege-escalation/dpapi-extracting-passwords.md)
- [From High Integrity to SYSTEM with Name Pipes](windows-hardening/windows-local-privilege-escalation/from-high-integrity-to-system-with-name-pipes.md)
- [Integrity Levels](windows-hardening/windows-local-privilege-escalation/integrity-levels.md)
Expand Down
6 changes: 3 additions & 3 deletions ...l-privilege-escalation/dll-hijacking/writable-sys-path-dll-hijacking-privesc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Writable Sys Path +Dll Hijacking Privesc
# Writable Sys Path +DLL Hijacking Privesc

{{#include ../../../banners/hacktricks-training.md}}

Expand All @@ -15,7 +15,7 @@ For more information about **DLL hijacking**, see:
./
{{#endref}}

## Privesc with Dll Hijacking
## Privesc with DLL Hijacking

### Finding a Missing DLL

Expand Down Expand Up @@ -66,7 +66,7 @@ if ($envPath -notlike "*$folderPath*") {
> [!TIP]
> **Boot logging is only required for services that start too early** to observe otherwise. If you can **trigger the target service/program on demand** (for example, by interacting with its COM interface, restarting the service, or relaunching a scheduled task), it is usually faster to keep a normal Procmon capture with filters such as **`Path contains .dll`**, **`Result is NAME NOT FOUND`**, and **`Path begins with <writable_machine_path>`**.

### Missed Dlls
### Missed DLLs

Running this in a free **virtual (vmware) Windows 11 machine** I got these results:

Expand Down