CVE-2017-5123 PoC — Linux kernel 输入验证错误漏洞

Source

Associated Vulnerability

Description

linux kernel exploit  

Readme

CVE-2017-5123
===================
Linux privilege escalation exploiting `waitid` syscall.  The exploit is brought
to you by [@XeR\_0x2A][] and [@chaign\_c][] from [HexpressoTeam][hexpresso] for
educational purposes only.  
The bug was introduced the 2017-05-21 and fixed 2017-10-09, 4.14.0-rc4+ is
known vulnerable.

[![asciicast](https://asciinema.org/a/BeRNWtrX27yF28CMeflqHQT0H.png)](https://asciinema.org/a/BeRNWtrX27yF28CMeflqHQT0H)

If you have a beginner/intermediate exploit writer level, we encourage you to
exploit it yourself before reading our implementation. It is a very good
exercise with an easy exploit primitive (arbitrary write to writable kernel
memory).  
We also challenge [@LiveOverflow][] to give it a try.

Here is the description:

> **oss-security:**  
> Hi,
> 
> Chris Salls discovered that when the waitid() syscall in Linux kernel  
> v4.13 was refactored, it accidentally stopped checking that the  
> incoming argument was pointing to userspace. This allowed local  
> attackers to write directly to kernel memory, which could lead to  
> privilege escalation.  
>  
> Introduced by this commit:  
> https://git.kernel.org/linus/4c48abe91be03d191d0c20cc755877da2cb35622  
>  
> Fixed with this commit to mainline tree:  
> https://git.kernel.org/linus/96ca579a1ecc943b75beba58bebb0356f6cc4b51  
>   
> This should be fixed in the -stable free (in the future v4.13.7) soon:  
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/log/?h=linux-4.13.y  
>   
> Thanks,

Spoiler !
-------------
> **waitid:**  
> waitid -- wait for a child process to change state.  
```c
int waitid(idtype_t idtype, id_t id, siginfo_t *infop, int options);
```

The kernel doesn't check whether `infop` is a kernelland or an userland
pointer, so we can overwrite memory of any kernel memory page with write
permissions. The fun part is that we only control partially what is written.  
There are more than a thousand ways to exploit this. We decided to turn this
write primitive into a null pointer dereference. We overwrote the
`have_canfork_callback` variable in the .BSS section of the kernel. Setting
this variable to anything else than 0 (true) will cause an unset
callback (null) to be "called on a new task before the process is exposed".

Thanks to Chris Salls and [@kees\_cook][] for sharing the CVE.

First "real world" linux kernel exploit of
[@XeR\_0x2A][] and
[@chaign\_c][] from
[HexpressoTeam][hexpresso].

> [chaignc+cve-2017-5123@hexpresso.team](mailto:chaignc+cve-2017-5123@hexpresso.team)  
> [xer+cve-2017-5123@hexpresso.team](mailto:xer+cve-2017-5123@hexpresso.team)

2017-10-22


[hexpresso]:     https://hexpresso.github.io
[@XeR\_0x2A]:    https://twitter.com/XeR_0x2A
[@chaign\_c]:    https://twitter.com/chaign_c
[@LiveOverflow]: https://twitter.com/LiveOverflow
[@kees\_cook]:   https://twitter.com/kees_cook

File Snapshot

 [4.0K]  /data/pocs/2a8283356de60487b2a99aee247c397117411624
├── [4.0K]  debug
│   ├── [6.8M]  bzImage
│   ├── [6.7M]  rootfs.img
│   ├── [ 519]  run_kernel.sh
│   ├── [ 513]  run_kernel.sh~
│   ├── [3.7M]  System.map
│   └── [ 34M]  vmlinux
├── [ 780]  kernel_compilation_cheatsheet.md
├── [2.8K]  README.md
└── [107K]  record.asciinema

1 directory, 9 files

Remarks