ReCACHE - Excessive Reflection, Type Confusion, and 0-Click ...#2333
Open
carlospolop wants to merge 1 commit into
Open
ReCACHE - Excessive Reflection, Type Confusion, and 0-Click ...#2333carlospolop wants to merge 1 commit into
carlospolop wants to merge 1 commit into
Conversation
Collaborator
Author
🔗 Additional ContextOriginal Blog Post: https://zhero-web-sec.github.io/research-and-things/re-cache-excessive-reflection-type-confusion-and-0-click-sxss-on-nextjs Content Categories: Based on the analysis, this content was categorized under "Pentesting Web -> Cache Poisoning and Cache Deception; Network Services Pentesting -> 80,443 - Pentesting Web Methodology -> NextJS; Pentesting Web -> XSS". Repository Maintenance:
Review Notes:
Bot Version: HackTricks News Bot v1.0 |
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
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.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
Overview
The blog describes a real-world zero-click stored XSS (SXSS) chain against a Next.js App Router application deployed behind Cloudflare cache. The root application mistake was unusual but highly dangerous: incoming request headers were mirrored into response headers. This allowed an attacker to inject response headers such as
Content-TypeandRefresh. Combined with Next.js React Serve...🔧 Technical Details
Response-header injection via request-header reflection: If an application mirrors incoming request headers into outgoing response headers, attacker-controlled request headers can become trusted response headers. This is dangerous even without HTTP response splitting because framework or application code may preserve attacker-set values. In this case, injecting
Content-Type: text/htmlchanged how the browser interpreted a framework-generated response, and injectingRefresh: 0; URLcreated browser-side navigation from a normal page to an attacker-selected URL.Next.js App Router RSC content-type confusion: In Next.js App Router, sending
Rsc: 1can request a React Server Component payload normally served astext/x-component. Dynamic RSC payloads may include URL parameters after the__PAGE__marker, and characters such as<and>may remain unescaped ...🤖 Agent Actions
Updated
src/network-services-pentesting/pentesting-web/nextjs.md.Added a new App Router technique covering:
Rsc: 1/ React Server Component response abuseContent-Type: text/htmloverride causing RSC-to-HTML type confusionRefreshon200 OKVary: Rsc,x-nextjs-prerender, CDN cache headers, and middleware/proxy matchersAlso appended references for:
RefreshOnly this file was changed.
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.