DEBIAN-CVE-2025-59437

Source
https://security-tracker.debian.org/tracker/CVE-2025-59437
Import Source
https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2025-59437.json
JSON Data
https://api.test.osv.dev/v1/vulns/DEBIAN-CVE-2025-59437
Upstream
Published
2025-09-16T06:16:05Z
Modified
2025-09-18T05:18:55Z
Summary
[none]
Details

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).

References

Affected packages

Debian:11 / node-ip

Package

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

Affected ranges

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:12 / node-ip

Package

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

Affected ranges

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:13 / node-ip

Package

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

Affected ranges

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:14 / node-ip

Package

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

Affected ranges

Ecosystem specific

{
    "urgency": "not yet assigned"
}