Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
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.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/ntgabrielgomes/cve-2023-20564
Privilege EscalationMemory ForensicsVulnerability AnalysisExploitationPenetration TestingHardware SecurityBinary Exploitation
GitHub
Share
ntgabrielgomes/cve-2023-20564

CVE-2023-20564

Proof-of-concept exploit for CVE-2023-20564 demonstrating arbitrary physical memory read/write via AMD Ryzen Master Driver IOCTL handlers, enabling privilege escalation on Windows.

View Repository
2034110 months agoReviewed by Kitploit

CVE-2023-20564 - AMD Ryzen Master Driver Physical Memory Access PoC

CVSS Platform

Overview

This repository contains a Proof of Concept (PoC) demonstrating the vulnerability CVE-2023-20564 in AMD Ryzen Master Driver. The vulnerability allows unprivileged users to read and write arbitrary physical memory, leading to potential privilege escalation and system compromise.

Vulnerability Details

  • CVE ID: CVE-2023-20564
  • CVSS Score: 8.8 (High)
  • Vendor: AMD
  • Product: AMD Ryzen Master Driver
  • Affected Versions: Multiple versions of AMD Ryzen Master software
  • Impact: Physical memory read/write access leading to privilege escalation

Technical Description

The AMD Ryzen Master driver (AMDRyzenMasterDriverV17.sys) contains insufficient validation in its IOCTL handlers, specifically:

  • Read IOCTL: 0x81112F08 - Allows reading arbitrary physical memory
  • Write IOCTL: 0x81112F0C - Allows writing arbitrary physical memory

The driver fails to properly validate:

  1. Physical memory addresses
  2. Size boundaries
  3. Protected memory regions

This allows malicious applications to:

  • Read sensitive kernel data structures
  • Modify critical system components
  • Bypass Windows kernel protections
  • Achieve arbitrary code execution in kernel mode

Files Needed

  • AMDRyzenMasterDriverV17.sys - The vulnerable driver file
  • Source code from this repository

2. Compile the PoC

# manually
g++ -std=c++17 poc_demo.cpp -o poc_demo.exe -ladvapi32

Key Components

Memory Structures

typedef struct _AMDReadStructure {
    LARGE_INTEGER PhysAddr;     // Physical address to read
    LARGE_INTEGER SizeAndData;  // Size and data buffer
    CHAR Buffer[1];             // Variable data buffer
} AMDReadStructure, *PAMDReadStructure;

Core Functions

  • ReadPhysicalMemory() - Read from physical memory
  • WritePhysicalMemory() - Write to physical memory
  • TestReadWriteVerify() - Complete test sequence
  • InstallDriverService() - Driver installation
  • StopAndRemoveDriverService() - Driver cleanup

Example Output

===========================================
  AMD Ryzen Master Driver - Memory PoC    
===========================================

[*] Installing and starting driver service...
[+] Driver file found
[+] Service created successfully
[+] Service started successfully

[*] Initializing driver connection...
[+] Driver connection established successfully

[!] TESTING READ/WRITE/VERIFY SEQUENCE

[STEP 1] Reading original data...
[*] Reading 8 bytes from physical address 0x100000
[*] PHYSICAL MEMORY READ SUCCESS!
    Read 8 bytes from 0x100000
    Data: 4D 5A 90 00 03 00 00 00

[STEP 2] Writing test data...
[*] Writing 8 bytes to physical address 0x100000
    Data: DE AD BE EF CA FE BA BE
[*] PHYSICAL MEMORY WRITE SUCCESS!
    Wrote 8 bytes to 0x100000

[STEP 3] Verifying written data...
[*] Reading 8 bytes from physical address 0x100000
[*] PHYSICAL MEMORY READ SUCCESS!
    Data: DE AD BE EF CA FE BA BE

[*] DATA VERIFICATION SUCCESS! Write/Read works correctly!

Technical Analysis

IOCTL Handler Analysis

The vulnerable driver exposes two main IOCTLs:

  1. Physical Memory Read (0x81112F08)

    • Input: Physical address + size
    • Output: Memory content at specified address
    • No validation of address ranges
  2. Physical Memory Write (0x81112F0C)

    • Input: Physical address + size + data
    • Output: None
    • No validation of protected memory regions

References

  • CVE-2023-20564 - MITRE
  • NVD Entry
  • AMD Security Advisory
  • Windows Driver Security Best Practices

Remember: This tool is for authorized security testing only. Always obtain proper permission before testing on any system.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    911
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    548
  • 3

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    366
  • 4

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    362
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    311
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    287

Explore all tools

Browse our collection of tools

View all tools →