Web Push Denial of Service via malicious Web Push endpoint
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-770.
Summary
Prior to version 0.10.3, the built-in clients of the `web-push` crate eagerly allocated memory based on the `Content-Length` header returned by the Web Push endpoint. Malicious Web Push endpoints could return a large `Content-Length` without ever having to send as much data, leading to denial of service by memory exhaustion. Services providing Web Push notifications typically allow the user to register an arbitrary endpoint, so the endpoint should not be trusted. The fixed version 0.10.3 now limits the amount of memory it will allocate for each response, limits the amount of data it will read from the endpoint, and returns an error if the endpoint sends too much data. As before, it is recommended that services add a timeout for each request to Web Push endpoints.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | web-push (crates.io) | before 0.10.4 | 0.10.4 | Patch available | GHSA-fc83-9jwq-gc2m |
- web-push (crates.io) Vendor— Affected before 0.10.4 Fixed in 0.10.4 Patch available GHSA-fc83-9jwq-gc2m
Remediation
- Fix · GHSA-fc83-9jwq-gc2m web-push (crates.io) Fixed in 0.10.4 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-fc83-9jwq-gc2m
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences