React-Server-Components-RCE

React Server Components 远程代码执行漏洞(CVE-2025-55182)

Other Affected Components

• Dify - AI application development platform
• NextChat - Chat application framework
• Other applications built on affected versions of React Server Components or Next.js

Note: If your application uses any of the versions listed above, it is recommended to upgrade to a secure version immediately or take appropriate protective measures.

✨ Features

🎯 Core Features

• Vulnerability Detection: Quickly detect whether the target has the React Server Components / Next.js RCE vulnerability
• Command Output: Execute system commands directly and obtain output results
• Memory Shell Injection: Inject a persistent webshell on the target server
• Reverse Shell: Obtain an interactive shell on the target system
• Batch Scanning: Support batch detection of multiple target URLs to quickly identify vulnerable systems

🔧 Auxiliary Features

• Proxy Support: Support HTTP proxy configuration (e.g., Burp Suite) for convenient traffic analysis
• Custom Headers: Add custom HTTP headers to bypass simple protections
• Real-time Logging: Operation logs displayed in real time for easy test tracking
• Timeout Setting: Customizable request timeout to adapt to different network environments

🚀 Quick Start

Requirements

• Java 8 or later
• Windows / Linux / macOS operating system

Launching the Tool

1. Double-click to run the React Server Components 远程RCE.jar file

2. Or start via command line:

   root@kitploit:~

   java -jar React Server Components 远程RCE.jar
   

3. On first launch, a disclaimer will be displayed. Please read it carefully and agree before continuing.

📋 Usage Guide

1️⃣ Basic Configuration

Before using any functionality, configure the basic information:

• Target URL: Enter the target website address (e.g., http://192.168.1.100:3000)
• Attack Path: The application path (default: /apps, adjustable based on the target)
• Timeout: Request timeout in seconds (default: 30 seconds)
• Custom Headers: Optional, one per line, format Header-Name: value

2️⃣ Vulnerability Detection

1. Fill in the target URL and basic configuration
2. Click the "Test Vulnerability" button
3. Wait for the detection result; the tool will automatically determine if the target is vulnerable

Tip: It is recommended to perform vulnerability detection first to confirm the target is vulnerable before proceeding with further operations.

🎮 Attack Mode Details

Mode 1: Command Output

Use case: Execute system commands and view the execution results

Steps:

1. Switch to the "Command Output" tab
2. Enter the command to execute in the command input box (e.g., whoami, ipconfig, ls -la)
3. Click the "Execute Command" button
4. View the command execution results in the text area below

Common command examples:

• Windows: whoami, ipconfig, dir, net user
• Linux: whoami, ifconfig, ls -la, uname -a

Mode 2: Memory Shell Injection

Use case: Leave a persistent backdoor on the target server

Steps:

1. Switch to the "Memory Shell Injection" tab

2. Set the memory shell access path (e.g., /exec)

3. Click the "Inject Memory Shell" button

4. After successful injection, you can execute commands via:

   root@kitploit:~

   Access: http://target-address/exec?cmd=whoami
   

Usage Notes:

• The memory shell is registered in the target application's memory and does not leave any files on disk
• The memory shell becomes invalid after the server restarts
• Pass the command to execute via the URL parameter cmd

Mode 3: Reverse Shell

Use case: Obtain an interactive shell on the target system

Steps:

1. Start a listener on your local machine (e.g., using netcat):

   root@kitploit:~

   nc -lvnp 4444
   

2. Switch to the "Reverse Shell" tab

3. Enter the listener IP (your machine's IP address)

4. Enter the listener port (e.g., 4444)

5. Click the "Send Reverse Shell" button

6. Go back to the netcat window and wait for the shell connection

Notes:

• Ensure the target server can reach your listener IP and port
• The firewall must allow inbound connections on the corresponding port
• In real environments, network policy restrictions may apply

Mode 4: Batch Detection

Use case: Perform vulnerability batch scanning on multiple targets

Steps:

1. Switch to the "Batch Detection" tab
2. Enter the list of target URLs in the text area (one per line)
3. Click the "Start Scan" button
4. View the scan results; the tool will mark targets that are vulnerable

⚙️ Advanced Configuration

Configuring HTTP Proxy

Used to forward traffic to packet capture tools such as Burp Suite, making it convenient to analyze requests and responses.

Configuration Steps:

1. Click the top menu "Settings" → "Proxy Settings"
2. Select "Enable"
3. Enter the proxy host (e.g., 127.0.0.1)
4. Enter the proxy port (e.g., 8080)
5. Click "Save"

Burp Suite Configuration:

• Ensure Burp Suite's proxy listener is started
• Default listener address: 127.0.0.1:8080
• In Burp, you can intercept and modify all requests sent by the tool

Proxy Status Display:

• After configuration, the proxy status will be shown in the upper right corner of the interface
• Green means enabled, gray means not configured

🛡️ Security Recommendations

1. Use only in authorized environments: Ensure you have explicit authorization before testing any target
2. Do not use in production environments: Avoid causing damage to production systems
3. Protect test data: Safeguard any sensitive information obtained during testing
4. Comply with laws and regulations: Unauthorized penetration testing may violate the law
5. CTF competition use: This tool is suitable for use in legal environments such as CTF events and training ranges

❓ Frequently Asked Questions

Q1: "No vulnerability detected" – What should I do?

Possible causes:

• The target URL is incorrect or the service is not running
• The target does not have this vulnerability
• The attack path is misconfigured
• Network unreachable or blocked by a firewall

Solutions:

• Check if the target URL is accessible normally
• Try adjusting the attack path parameter
• Check network connectivity and proxy settings

Q2: No output after executing a command?

Possible causes:

• The command executed successfully but produced no output (e.g., certain file-writing commands)
• Permissions are restricted on the target system
• Command syntax error

Solutions:

• Try executing a command with clear output (e.g., id)
• Check if the command syntax is correct
• Review the detailed information in the log area at the bottom

Q3: Reverse shell connection fails?

Possible causes:

• The target cannot reach your listener IP
• The firewall is blocking the connection
• The port is already in use

Solutions:

• Confirm that the listener service is started (nc -lvnp port)
• Check firewall settings to allow the corresponding port
• Ensure the IP address is filled in correctly (if the target and you are on the same internal network, use the internal IP)

Q4: How to view detailed requests and responses?

Solutions:

• Configure an HTTP proxy (e.g., Burp Suite)
• View the complete HTTP traffic in the proxy tool
• The log area at the bottom also displays key information

📞 Technical Support

• Author: CrabSec
• Version: v1.0.0

📜 Copyright Notice

This tool is provided for learning and authorized security testing only. All consequences arising from the use of this tool are the responsibility of the user. The developer assumes no liability.

Please comply with cybersecurity laws and regulations, and be an ethical security researcher!

Happy testing! 🎉