DEBIAN-CVE-2020-15168

Source
https://security-tracker.debian.org/tracker/CVE-2020-15168
Import Source
https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2020-15168.json
JSON Data
https://api.test.osv.dev/v1/vulns/DEBIAN-CVE-2020-15168
Upstream
Published
2020-09-10T19:15:13Z
Modified
2025-09-19T06:25:13Z
Summary
[none]
Details

node-fetch before versions 2.6.1 and 3.0.0-beta.9 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.

References

Affected packages

Debian:11 / node-fetch

Package

Name
node-fetch
Purl
pkg:deb/debian/node-fetch?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
2.6.1-2

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:12 / node-fetch

Package

Name
node-fetch
Purl
pkg:deb/debian/node-fetch?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
2.6.1-2

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:13 / node-fetch

Package

Name
node-fetch
Purl
pkg:deb/debian/node-fetch?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
2.6.1-2

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:14 / node-fetch

Package

Name
node-fetch
Purl
pkg:deb/debian/node-fetch?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
2.6.1-2

Ecosystem specific

{
    "urgency": "not yet assigned"
}