Description
The ip (aka node-ip) package through 2.0.1 (in NPM) might allow SSRF because the IP address value 0 is improperly categorized as globally routable via isPublic. NOTE: this issue exists because of an incomplete fix for CVE-2024-29415. NOTE: in current versions of several applications, connection attempts to the IP address 0 (interpreted as 0.0.0.0) are blocked with error messages such as net::ERR_ADDRESS_INVALID. However, in some situations that depend on both application version and operating system, connection attempts to 0 and 0.0.0.0 are considered connection attempts to 127.0.0.1 (and, for this reason, a false value of isPublic would be preferable).
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| fedorindutny | ip | ≤ 2.0.1 | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | node-ip | No fix yet | — |
| Debian 13 | node-ip | No fix yet | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | node-ip | No fix yet | — |
| Ubuntu 26.04 LTS | node-ip | No fix yet | — |
| Ubuntu 25.10 | node-ip | No fix yet | — |
| Ubuntu 24.04 LTS | node-ip | No fix yet | — |
Show 3 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu Pro 22.04 LTS | node-ip | No fix yet | — |
| Ubuntu Pro 20.04 LTS | node-ip | No fix yet | — |
| Ubuntu Pro 18.04 LTS | node-ip | No fix yet | — |