How to fix: Service Worker with insecure fetch handler
The Service Worker intercepts all requests but does not validate origins or enforce HTTPS, potentially caching insecure responses.
Why it matters
An insecure Service Worker can cache and serve HTTP responses, downgrade HTTPS connections, and intercept all network traffic for the origin, extending the impact of any compromise beyond the page lifetime.
Service Workers should only intercept requests to known origins, enforce HTTPS, and not cache sensitive data.
How to fix it
- 1Limit fetch interception to same-origin requests
- 2Do not cache responses from HTTP origins
- 3Avoid caching responses with authentication data (Authorization headers)
Code examples
Register service worker only on HTTPS
// Service workers require HTTPS (except localhost)
if ('serviceWorker' in navigator && location.protocol === 'https:') {
navigator.serviceWorker.register('/sw.js')
.catch(err => console.error('SW registration failed:', err));
}References
Detected automatically by VulnRadar. The check id is sw-insecure, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is Service Worker with insecure fetch handler?
- VulnRadar rates this medium severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id sw-insecure, which stays the same between runs so you can filter, diff, or gate CI on it.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.