SkillAgentSearch skills...

GhostWriteExploit

Supporting code for exploiting the RISC-V GhostWrite vulnerability

Install / Use

/learn @LaurieWired/GhostWriteExploit
About this skill

Quality Score

0/100

Supported Platforms

Universal

README

GhostWrite Exploit :ghost:

Welcome to the GhostWrite Exploits repository, where we use the GhostWrite RISC-V CPU vulnerability to directly manipulate physical memory! :computer:

What is this repository? :mag_right:

This repository contains two PoCs for exploiting hardware vulnerabilities in the XuanTie C910 processor:

  1. System Crash PoC: Continuously writing junk data to physical memory, causing the system to crash.
  2. Inter-Process Memory Modification: Exploiting physical memory access to modify the memory of a separate running process.

These PoCs are based on the paper and research from GhostWriteAttack.com by researchers at the CISPA Helmholtz Center for Information Security.

Why is this important? :thinking:

  • Hardware Vulnerabilities: Unlike software bugs, hardware vulnerabilities like GhostWrite are significantly harder to patch and may have no solution.
  • Physical Memory Access: These PoCs demonstrate how access to physical memory can lead to system-wide control and crash scenarios.
  • Learn & Experiment: If you're a student or researcher, you can experiment with these vulnerabilities using real hardware. This is your opportunity to understand hardware exploitation and the risks it poses.

Getting Started :runner:

Here's how to get started with the PoCs:

  1. Clone this repository:
    git clone https://github.com/LaurieWired/GhostWriteExploit.git
    
  2. Choose a folder:
    • Crash PoC: Explore the folder CrashSystem/ to see how we crash the system by writing to physical memory.
    • Memory Modification PoC: Explore the folder OverwriteProcess/ to see how one process can directly modify the memory of another.
  3. Build the code:
    • To compile directly on the native RISC-V board:
    gcc ghostwrite.c -o ghostwrite -march="rv64gzve64x"
    
  4. Run the PoCs:
    • Crash the system: Run the system crash executable and see the CPU bug in action.
    • Modify another process's memory: Run the second PoC to witness how physical memory access can manipulate a separate process.

Accompanying Video :video_camera:

If you want more explanations of the vulnerability, watch the accompanying video on YouTube!

Related Skills

View on GitHub
GitHub Stars84
CategoryCustomer
Updated4d ago
Forks4

Languages

C

Security Score

80/100

Audited on Mar 30, 2026

No findings