ScottyBauer/Android_Kernel_CVE_POCs logo

ScottyBauer/Android_Kernel_CVE_POCs

Free

A list of my CVE's with POCs

FreeFree tier
Type
Open Source

About ScottyBauer/Android_Kernel_CVE_POCs

This repository houses a series of Proof-of-Concept (PoC) C programs that trigger vulnerabilities found in the Android kernel. It includes CVE entries from 2015 to 2018, covering a variety of kernel exploits. Some exploits are specific to MediaTek devices (marked with _mtk.c) and may not have been tested on actual hardware. The repository is maintained by Scotty Bauer and is available on GitHub as an open-source resource for security researchers and Android developers.

Key Features

Proof-of-concept C programs for Android kernel vulnerabilities
Covers CVE entries from 2015 to 2018 (e.g., CVE-2015-0572, CVE-2016-0822, CVE-2017-8259, CVE-2018-9355)
Includes exploits for both generic and MediaTek-specific vulnerabilities
Open-source and freely available on GitHub
Developed and maintained by Scotty Bauer (see plzdonthack.me for full list)

Pros & Cons

Pros
  • Provides working proof-of-concept code for real CVEs
  • Free and open source, accessible to anyone
  • Covers multiple years of Android kernel vulnerabilities
  • Includes exploits for both common and MediaTek-specific chipsets
Cons
  • Only includes C source code, no precompiled binaries or build scripts
  • Some exploits marked _mtk.c may not be tested on actual MediaTek devices
  • Requires knowledge of Android kernel development and cross-compilation to use
  • Limited to vulnerabilities found by the author; not a comprehensive database of all Android kernel CVEs

Best For

Security research into Android kernel vulnerabilitiesTesting Android devices for kernel exploitabilityEducational reference for kernel exploit developmentDeveloping and testing mitigation techniques

FAQ

What does this repository contain?
It contains a series of Proof-of-Concept C programs that trigger vulnerabilities (CVEs) found in the Android kernel by Scotty Bauer. The repository includes exploits from 2015 to 2018.
What programming language are the exploits written in?
All exploits are written in C, as indicated by the .c file extensions.