MITRE ATT&CK · T1068

Exploitation for Privilege Escalation

MITRE · cited in 68 of our lessons

Explanation

What attackers do. Attackers exploit a software bug, often in the operating system kernel, a driver or a privileged service, to raise their access from a normal user to administrator or system level. This serves the Privilege Escalation tactic and sometimes Defence Evasion.

How to defend. Patch operating systems, drivers and privileged software promptly, and use vulnerable driver blocklists to stop attackers loading known-flawed signed drivers. Limit local admin rights so that exploitation is needed at all, and enable exploit protection features available in the platform. Endpoint detection tools that monitor process integrity levels and driver loads give the best visibility.

Signs to look for. Watch for a low-privilege process suddenly spawning a child running as system, unexpected driver installations, and crashes of privileged services just before suspicious activity. Gaps often come from unpatched legacy hosts and from not alerting on driver loads at all.

The official text
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges. Exploitation of a software vulnerability occurs when an adversary takes advantage of a programming error in a program, service, or within the operating system software or kernel itself to execute adversary-controlled code. Security constructs such as permission levels will often hinder access to information and use of certain techniques, so adversaries will likely need to perform privilege escalation to include use of software exploitation to circumvent those restrictions. When initially gaining access to a system, an adversary may be operating within a lower privileged process which will prevent them from accessing certain resources on the system. Vulnerabilities may exist, usually in operating system components and software commonly running at higher permissions, that can be exploited to gain higher levels of access on the system. This could enable someone to move from unprivileged or user level permissions to SYSTEM or root permissions depending on the component that is vulnerable. This could also enable an adversary to move from a virtualized environment, such as within a virtual machine or container, onto the underlying host. This may be a necessary step for an adversary compromising an endpoint system that has been properly configured and limits other privilege escalation methods. Adversaries may bring a signed vulnerable driver onto a compromised machine so that they can exploit the vulnerability to execute code in kernel mode. This process is sometimes referred to as Bring Your Own Vulnerable Driver (BYOVD). Adversaries may include the vulnerable driver with files delivered during Initial Access or download it to a compromised system via Ingress Tool Transfer or Lateral Tool Transfer.

© The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation (MITRE ATT&CK®).

Lessons that cite it

Real incidents where this item mattered: the latest 12 of 68.