When reading an HTTP response from a server, if no read amount is specified, the default behavior will be to use Content-Length. This allows a malicious server to cause the client to read large amounts of data into memory, potentially causing OOM or other DoS.
Metrics
Affected Vendors & Products
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Mon, 01 Dec 2025 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
ssvc
|
Mon, 01 Dec 2025 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | When reading an HTTP response from a server, if no read amount is specified, the default behavior will be to use Content-Length. This allows a malicious server to cause the client to read large amounts of data into memory, potentially causing OOM or other DoS. | |
| Title | Excessive read buffering DoS in http.client | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: PSF
Published:
Updated: 2025-12-01T19:00:52.546Z
Reserved: 2025-12-01T17:54:40.759Z
Link: CVE-2025-13836
Updated: 2025-12-01T18:32:42.784Z
Status : Received
Published: 2025-12-01T18:16:04.200
Modified: 2025-12-01T19:15:49.770
Link: CVE-2025-13836
No data.
OpenCVE Enrichment
No data.