Node Fetch did not honor the size
option after following a redirect, which means that when a content size was over the limit, a FetchError
would never get thrown and the process would end without failure.
For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don't double-check the size of the data after fetch()
has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.
We released patched versions for both stable and beta channels:
v2
: 2.6.1v3
: 3.0.0-beta.9None, it is strongly recommended to update as soon as possible.
If you have any questions or comments about this advisory: * Open an issue in node-fetch * Contact one of the core maintainers.
{ "nvd_published_at": null, "cwe_ids": [ "CWE-20", "CWE-770" ], "severity": "LOW", "github_reviewed": true, "github_reviewed_at": "2020-09-10T17:44:09Z" }