Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE202015808 — A proof of concept of CVE-2020-15808 vulnerability exploit on STM32F4 Discovery board | Kitploit
Tools/GitHubGitHub/manucuf/cve202015808
Embedded Systems SecurityVulnerability AnalysisExploitationHardware SecurityFirmware AnalysisBinary Exploitation
GitHubmanucuf/cve202015808

CVE202015808

A proof of concept of CVE-2020-15808 vulnerability exploit on STM32F4 Discovery board

View Repository
7135 years agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2020-15808

A proof of concept of CVE-2020-15808 vulnerability exploit on STM32F4 Discovery board

Requirements

  • Firmware version older than 1.25.2
  • Board with VCP (ex. STM32F4 discovery)
  • arm-none-eabi toolchain

Steps to reproduce the exploit

  1. Move to VulnerableFirmwareF4 and compile through

    make

    Ignore warnings due to unused variable, they are needed to ensure the compiler does not omit the variable

  2. Flash build/VulnerableFirmware.elf on the device

  3. Connect the Virtual Com Port

  4. Get the list of connected devices through

    lsusb

    Get the hex values corresponding to STM32 Virtual Com Port. They will be Vendor Id (VID) and Product Id (PID)

  5. Edit main.c replacing to VID and PID macro with the found values. Default are for STM32F4 Discovery

  6. Compile main.c

    gcc main.c

  7. Execute a.out with root permission

    sudo ./a.out

  8. In order to view the dump use

    hexdump -C result.bin



Example dump of xcube-cryptolib

Follow the same instruction for VulnerableFirmwareF4_cryptolib. The content of AESctx should start from 0x1b2c offset from dump

Download Tool