⭕Privilege Escalation
Last updated
Last updated
1. first rule of privilege escalation is that you HAVE TO be familiar with target system command line, actually the more comfortable you are with the shell the better and easier will be the privesc phase.
2. DO NOT jump to kernel exploits FIRST. yes, yes, in a CTF its a low-hanging fruit but in a real life scenario you dont want to crash the system SPECIALLY web and file servers, do you?
3. whatever tool you use for prives or whats called the post-exploitation information gathering, remember you should use manual techniques too. make sure you didnt miss anything.
4. all privilege escalations are effectively examples of access control violations. so if you can access what you want, there is usually no need to gain a root shell, except in a CTF or when you're trying to impress your client.
a list of automated tools used in post-exploitation enumeration and privilege escalation.
unlike linux, in windows you have to consider the possibility that the any tool you are going to use may trigger a defensive mechanism such as AVs or an HIPS/HIDS so for operational security, its better to use obfuscated versions of these tools because even the harmless scripts such as powerview will be detected by most AV vendors out there.
the other reasonable way to stay under the radar in a real-world pentest is to use commands and tools that are already available on the target system such as wmic and powershell cmdlets. but keep in mind that in some environments with strict access control/delegation even running any powershell commands might trigger a sensor.
as far as opsec is concerned, non of the tools mentioned bellow can evade AV products by default, mainly because of their signatures.
