Changes in 43.8.3
- Check the position of all the cutoffs of the keynav page
- The client stores its cutoffs at the positions from 1 to last - 1
- A page array with a cutoff missing from those positions, or present outside them, restarts from page 1
- A forged next cutoff can no longer produce a next page beyond the last one
- Noted by Zac (7a6163) in the review of the fix
- Restart the keyset pagination when the page param is not a cutoff
- A page param that decodes to an integer or a string no longer raises
- A page param that is not an array of the keyset size restarts from the first page
- Noted by Zac (7a6163) in the review of the fix
- Restart the keynav pagination when the page cutoff does not match the page position
- Only the last page has no cutoff: a page array that says otherwise restarts from page 1
- A forged page can no longer produce a next page beyond the last one
- Suggested by Zac (7a6163) in the review of the fix
- Share the keynav storage key among the navs of the same pagination
- The navs of a new pagination created a storage key each, leaving unused entries in the sessionStorage
- A re-rendered series_nav_js created a new one at each rendering
- Merge the short and empty visited keynav pages
- A short page is merged with the next page when their records fit in the limit
- An empty page is always replaced by the next page
- A short page followed by the last page is filled from it
- The clients that do not guard the updates keep their pages
- Limit the records of the visited keynav pages
- A visited page is fetched with a limit, so a forged cutoff cannot pull the whole set
- A page grown beyond the limit is split: its new cutoff is inserted before the old one
- The clients that do not guard the updates get the old cutoff replaced
- Reported by Zac (7a6163) in GHSA-v472-jp5g-c53f
- Skip the keynav cutoffs update generated by a stale page
- The client sends also the cutoff of the next page
- The server returns the cutoffs it received with the update
- The client updates its cutoffs only if they are still the ones the server received
- Reloading an old URL no longer overwrites the stored cutoffs
- Validate the keynav page param and require a matching cookie
- The page array restarts from page 1 when its types or its range are wrong
- A missing cookie no longer matches a null browser key
- A page param that does not decode to an array no longer raises
- Reported by Zac (7a6163) in GHSA-h648-g954-826q
Upgrading from version 9 or earlier? See the Upgrade Guide.