React Router DOM offers declarative routing solutions tailored for React web applications, providing developers with the tools to manage navigation and create engaging user experiences. Comparing versions 7.1.2 and 7.1.1 reveals subtle yet potentially important distinctions. Both versions share the same core description and dependencies, relying on react-router for routing functionality. They also maintain identical development dependencies (tsup, react, wireit, react-dom, typescript) and peer dependencies, ensuring compatibility with React 18 and later. The license, repository details, and author information remain consistent across both releases.
Key differences lie in the version numbers of the internal dependency react-router version which matches the host package version, and the release dates with version 7.1.2 was published after version 7.1.1. Developers should leverage the newest version, 7.1.2, primarily to access the latest bug fixes, performance enhancements, and any potential security patches incorporated since the 7.1.1 release. Checking the changelog associated with the related react-router package (7.1.2 vs 7.1.1) is highly recommended for a detailed understanding of specific changes. Always prioritize staying up-to-date with the most recent stable releases to maintain application stability and security.
All the vulnerabilities related to the version 7.1.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.