Fix React Server Components RCE vulnerability #16
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
## React Flight / Next.js RCE Advisory Patch Implementation ### Summary Updated the repository to address the React Flight / Next.js RCE advisory by upgrading Next.js to a patched version. The project was confirmed to be affected and has been successfully patched. ### Vulnerability Detection - ✅ Project uses Next.js: `[email protected]` - ✅ No React Flight packages detected (not vulnerable directly) - ✅ Project affected via Next.js dependency ### Changes Made #### 1. Upgraded Next.js (package.json) - **File**: `package.json` - **Change**: Upgraded `next` from `15.0.0-canary.152` to `15.0.5` - The version `15.0.0-canary.152` falls under the `15.0.x` category - Per the advisory, `15.0.x` versions should be patched to `15.0.5` #### 2. Updated Lockfile (pnpm-lock.yaml) - **File**: `pnpm-lock.yaml` - **Action**: Ran `pnpm install` to resolve dependencies - **Verification**: Lockfile now contains `[email protected]` and all dependencies are correctly resolved #### 3. Fixed Next.js 15 Compatibility Issue (utils/kasada/kasada-server.ts) - **File**: `utils/kasada/kasada-server.ts` - **Issue**: Next.js 15 removed the `request.ip` property from NextRequest - **Solution**: Updated code to extract IP from headers using `request.headers.get("x-real-ip")` or `request.headers.get("x-forwarded-for")` - **Locations fixed**: 3 locations where `request.ip` was used ### Build Verification - ✅ `pnpm install` completed successfully with all dependencies resolved - ✅ `next build` completed successfully with no errors - ✅ All routes compiled without type or compilation errors - ✅ Production build output generated successfully ### Notes - React and react-dom were NOT modified (they are not vulnerable) - No React Flight packages were found in the project, so no action needed there - The Next.js upgrade is the only required change for this RCE vulnerability - The compatibility fix in kasada-server.ts was necessary to maintain build stability after the Next.js upgrade Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Author
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A critical remote code execution (RCE) vulnerability in React Server Components, impacting frameworks such as Next.js, was identified in the project ai-sdk-preview-internal-knowledge-base. The vulnerability enables unauthenticated RCE on the server via insecure deserialization in the React Flight protocol.
This issue is tracked under:
This automated pull request upgrades the affected React and Next.js packages to patched versions that remediate the issue.
More Info