A municipal elevated application loads DLLs from a path writable by a standard user. What privilege-escalation class should the tester investigate carefully?
Select an answer to reveal the explanation.
Short Explanation
If a privileged app looks for a DLL in a folder you can write, you may get to plant the library it trusts. That DLL hijack class needs careful validation—false paths happen. It is about load order and ACLs, not Secure Boot or zone transfers.
Full Explanation
DLL search-order issues arise when elevated processes resolve libraries from directories writable by lesser users, enabling hijack-class privilege escalation. Testers should confirm writability, search order, and that the elevated process actually loads the candidate module before claiming impact. The finding does not by itself prove Secure Boot state, DNS zone-transfer problems, or PowerShell language-mode enforcement. Careful validation keeps reports accurate and RoE-safe.