You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
|
|
# Linux Kernel ROP demo
|
|
|
|
|
|
|
|
|
|
This is a vulnerable Linux kernel driver used to demonstrate in-kernel
|
|
|
|
|
privilege escalation ROP (Return Oriented Programming) chain in practice. The
|
|
|
|
|
article URL for Part 1 is available at
|
|
|
|
|
<https://cyseclabs.com/page?n=17012016>.
|
|
|
|
|
|
|
|
|
|
The driver module is vulnerable to OOB access and allows arbitrary code
|
|
|
|
|
execution. An arbitrary offset can be passed from user space via the provided
|
|
|
|
|
ioctl(). This offset is then used as the index for the 'ops' array to obtain
|
|
|
|
|
the function address to be executed.
|
|
|
|
|
|
|
|
|
|
* drv.c - vulnerable kernel driver
|
|
|
|
|
* trigger.c - user-space application to trigger the OOB access via the provided
|
|
|
|
|
ioctl
|
|
|
|
|
|
|
|
|
|
The goal is to construct and execute a ROP chain that will satisfy the
|
|
|
|
|
following requirements:
|
|
|
|
|
|
|
|
|
|
* Execute a privilege escalation payload
|
|
|
|
|
* Data residing in user space may be referenced (i.e., "fetching" data from
|
|
|
|
|
user space is allowed)
|
|
|
|
|
* Instructions residing in user space may not be executed
|
