react-router
Affected
- introduced
7.2.0, fixed7.5.2(semver)
Fixed versions
7.5.2
Fix
- Fixed version
7.5.2npm install [email protected]
Advisory
Also known as: CVE-2025-43864
React Router allows a DoS via cache poisoning by forcing SPA mode
Summary
After some research, it turns out that it is possible to force an application to switch to SPA mode by adding a header to the request. If the application uses SSR and is forced to switch to SPA, this causes an error that completely corrupts the page. If a cache system is in place, this allows the response containing the error to be cached, resulting in a cache poisoning that strongly impacts the availability of the application.
Details
The vulnerable header is X-React-Router-SPA-Mode; adding it to a request sent to a page/endpoint using a loader throws an error. Here is the vulnerable code :
<img width="672" alt="Capture d’écran 2025-04-07 à 08 28 20" src="https://github.com/user-attachments/assets/0a0e9c41-70fd-4dba-9061-892dd6797291" />
To use the header, React-router must be used in Framework mode, and for the attack to be possible the target page must use a loader.
Steps to reproduce
Versions used for our PoC:
routes/ssr)/ssr in our case) adding the following header:X-React-Router-SPA-Mode: yes
Notice the difference between a request with and without the header;
Normal request
Capture d’écran 2025-04-07 à 08 36 27
With the header
Capture d’écran 2025-04-07 à 08 37 01
image
Impact
If a system cache is in place, it is possible to poison the response by completely altering its content (*by an error message*), strongly impacting its availability, making the latter impractical via a cache-poisoning attack.
Credits
High Basis: The source's own band: HIGH
7.2.0, fixed 7.5.2 (semver)7.5.2
7.5.2npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0