CVE-2025-59437: SSRF
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::ERRADDRESSINVALID. 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 Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-59437?
CVE-2025-59437 has a Medium severity rating due to its ability to cause Server-Side Request Forgery (SSRF).
How do I fix CVE-2025-59437?
To fix CVE-2025-59437, update the ip package to a version later than 2.0.1 where the vulnerability has been patched.
What software is affected by CVE-2025-59437?
CVE-2025-59437 affects the ip package in versions up to and including 2.0.1 available via NPM.
What kind of vulnerability is CVE-2025-59437?
CVE-2025-59437 is categorized as a Server-Side Request Forgery (SSRF) vulnerability.
What causes CVE-2025-59437?
CVE-2025-59437 is caused by improper categorization of the IP address value 0 as globally routable within the ip package.