React Router has released version 7.0.2, a minor update following the previous stable version 7.0.1. Both versions maintain the core functionality of declarative routing for React applications and share identical dependencies, including "cookie," "turbo-stream," "@types/cookie," and "set-cookie-parser." Similarly, the development dependencies for testing and building the library remain the same, featuring tools like "tsup," "react," "rimraf," "wireit," "react-dom," "typescript," and "@types/set-cookie-parser." The peer dependencies specify that React Router is compatible with React and React DOM versions 18 and above.
A notable difference lies in the "dist" object, specifically the "unpackedSize," which has subtly increased from 2268855 bytes in version 7.0.1 to 2270456 bytes in version 7.0.2. This suggests minor internal adjustments or fixes that contribute to the overall size, though the file count remains constant. The release date also provides a clear distinction, indicating that version 7.0.2 was published on December 3, 2024, whereas version 7.0.1 was released on November 22, 2024.
Developers considering upgrading should be aware that the fundamental routing mechanisms and API remain consistent, with the update focusing on under-the-hood improvements. It would be wise to check the changelog for more information on specific adjustments. Given that it's a minor version increment, the update process should be straightforward, offering potentially enhanced stability and performance without requiring significant code modifications to existing React Router implementations. Upgrading should be safe and bring marginal gains in performance.
All the vulnerabilities related to the version 7.0.2 of the package
React Router allows pre-render data spoofing on React-Router framework mode
After some research, it turns out that it's possible to modify pre-rendered data by adding a header to the request. This allows to completely spoof its contents and modify all the values of the data object passed to the HTML. Latest versions are impacted.
The vulnerable header is X-React-Router-Prerender-Data, a specific JSON object must be passed to it in order for the spoofing to be successful as we will see shortly. Here is the vulnerable code :
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.
Versions used for our PoC:
routes/ssr).data. In our case the page is called /ssr:We access it by adding the suffix .data and retrieve the data object, needed for the header:
X-React-Router-Prerender-Data header with the previously retrieved object as its value. You can change any value of your data object (do not touch the other values, the latter being necessary for the object to be processed correctly and not throw an error):As you can see, all values have been changed/overwritten by the values provided via the header.
The impact is significant, if a cache system is in place, it is possible to poison a response in which all of the data transmitted via a loader would be altered by an attacker allowing him to take control of the content of the page and modify it as he wishes via a cache-poisoning attack. This can lead to several types of attacks including potential stored XSS depending on the context in which the data is injected and/or how the data is used on the client-side.