The `fetch()` API and navigation incorrectly shared the...
Critical severity
Unreviewed
Published
Feb 20, 2024
to the GitHub Advisory Database
•
Updated Aug 20, 2024
Description
Published by the National Vulnerability Database
Feb 20, 2024
Published to the GitHub Advisory Database
Feb 20, 2024
Last updated
Aug 20, 2024
The
fetch()
API and navigation incorrectly shared the same cache, as the cache key did not include the optional headersfetch()
may contain. Under the correct circumstances, an attacker may have been able to poison the local browser cache by priming it with afetch()
response controlled by the additional headers. Upon navigation to the same URL, the user would see the cached response instead of the expected response. This vulnerability affects Firefox < 123.References