Difference between revisions of "Exploit Methods/Userspace execution"
Jump to navigation
Jump to search
| Line 38: | Line 38: | ||
| hardware PXN (Address Spaces) | | hardware PXN (Address Spaces) | ||
|- | |- | ||
|rowspan=" | |rowspan="4"| powerpc | ||
| radix MMU (since POWER9) | | radix MMU (since POWER9) | ||
| hardware PXN (KUEP, since Linux v4.10) | | hardware PXN (KUEP, since Linux v4.10) | ||
Latest revision as of 12:33, 31 July 2019
Details
Once an attacker has gain control over the instruction pointers, it must be aimed somewhere. The place where attackers have the most control over memory layout tends to be in userspace, so it has been natural to place malicious code in userspace and have the kernel redirection execution there. (Frequently known as "ret2usr".)
For more details, see Userspace access, as that can be superset of userspace execution under some emulation situations.
Examples
- See nearly every other exploit example listed under other Exploit Methods and Bug Classes.
Mitigations
- hardware segregation: SMEP (x86), PXN (arm)
- compiler instrumentation to set high bit on function calls
- emulate memory segregation via separate page tables (e.g. PAX_MEMORY_UDEREF)
Right now, the upstream options available for Privileged eXecute Never (e.g. PXN, SMEP) are:
| CPU | Feature Name | |
|---|---|---|
| ARM | v7 (32-bit) non-LPAE | CONFIG_CPU_SW_DOMAIN_PAN (since Linux v4.3) |
| v7 (32-bit) LPAE (e.g. Cortex-A7, A15+) | hardware PXN (since Linux v3.19) | |
| v8.0+ (64-bit) | hardware PXN | |
| x86 | pre-Ivy-Bridge | nothing (could use PCID?) |
| Ivy-Bridge+ (since May 2012) | hardware PXN (SMEP) | |
| s/390 | hardware PXN (Address Spaces) | |
| powerpc | radix MMU (since POWER9) | hardware PXN (KUEP, since Linux v4.10) |
| PPC64 hash MMU (since POWER7) | nothing yet, but implementation possible | |
| PPC32 hash MMU (except 601 which doesn't have NX segment) | hardware PXN (KUEP) | |
| MPC 8xx | hardware PXN (KUEP) | |
| MIPS | nothing (could use ASID switching?) | |