fetch(url) leads to a memory leak in undici
### Impact Calling `fetch(url)` and not consuming the incoming body ((or consuming it very slowing) will lead to a memory leak. ### Patches Patched in v6.6.1 ### Workarounds Make sure to always consume the incoming body.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2024-24750US | medium6.5 | — | ||
Undici is an HTTP/1.1 client, written from scratch for Node.js. In affected versions calling `fetch(url)` and not consuming the incoming body ((or consuming it very slowing) will l… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/nodejs/undiciPACKAGE
- https://github.com/nodejs/undici/commit/87a48113f1f68f60aa09abb07276d7c35467c663WEB
- https://github.com/nodejs/undici/releases/tag/v6.6.1WEB
- https://github.com/nodejs/undici/security/advisories/GHSA-9f24-jqhm-jfcwWEB
- https://nvd.nist.gov/vuln/detail/CVE-2024-24750ADVISORY
- https://security.netapp.com/advisory/ntap-20240419-0006WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan