Next.js RSC RCE Scanner Burp Suite Extension #1654
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
The repository provides a Burp Suite extension called Next.js RSC RCE Scanner, a high-fidelity active scanner for detecting Next.js / React Server Components (RSC) Remote Code Execution vulnerabilities CVE-2025-55182 and CVE-2025-66478 in default App Router configurations.
How the underlying vulnerability works
Next.js uses React Server Components (RSC), which are streamed over the network an...
🔧 Technical Details
RSC error-signature based detection for Next.js RCE (CVE-2025-55182 & CVE-2025-66478)
The core hacking trick is to detect RCE-prone React Server Components (RSC) bugs in Next.js by abusing the way RSC parsers (
react-server-dom-parcel,react-server-dom-turbopack,react-server-dom-webpack) handle colon-delimited property access inside streamed RSC data. An attacker (or scanner) sends a multipart HTTP request carrying an RSC stream crafted so that the parser performs a property lookup on anundefinedobject. This reliably causes an internal RSC parsing error, leading to a 500 HTTP response and an RSC error frame in the body beginning withE{"digest". By programmatically injecting this malformed RSC multipart payload into endpoints and then checking responses for the combined signaturestatus == 500and body containingE{"digest...🤖 Agent ActionsSummary:
src/network-services-pentesting/pentesting-web/nextjs.mdwith a dedicated subsection on high-fidelity detection of the Next.js/React Server Components colon-delimited crash that underpins CVE-2025-55182/66478. The new content explains the crafted multipart Flight payload, outlines the500 + E{"digest"response signature, and details how the Burp-based Next.js RSC RCE Scanner automates both active and manual scans while remaining a “detection-only” payload.Tests: Not run (not requested).
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.