Debian Package Tracker
Register | Log in
Subscribe

node-ip

IP address utilities for node.js

Choose email to subscribe with

general
  • source: node-ip (main)
  • version: 2.0.1+~1.1.3-3
  • maintainer: Debian Javascript Maintainers (archive) (DMD)
  • uploaders: suman [DMD]
  • arch: all
  • std-ver: 4.7.2
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 1.1.5-5
  • oldstable: 2.0.0+~1.1.0-1
  • stable: 2.0.1+~1.1.3-3
  • testing: 2.0.1+~1.1.3-3
  • unstable: 2.0.1+~1.1.3-3
versioned links
  • 1.1.5-5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.0.0+~1.1.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.0.1+~1.1.3-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • node-ip
action needed
3 security issues in bookworm high

There are 3 open security issues in bookworm.

1 important issue:
  • CVE-2025-59437: 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).
2 issues left for the package maintainer to handle:
  • CVE-2023-42282: (needs triaging) The ip package before 1.1.9 for Node.js might allow SSRF because some IP addresses (such as 0x7f.1) are improperly categorized as globally routable via isPublic.
  • CVE-2024-29415: (needs triaging) The ip package through 2.0.1 for Node.js might allow SSRF because some IP addresses (such as 127.1, 01200034567, 012.1.2.3, 000:0:0000::01, and ::fFFf:127.0.0.1) are improperly categorized as globally routable via isPublic. NOTE: this issue exists because of an incomplete fix for CVE-2023-42282.

You can find information about how to handle these issues in the security team's documentation.

Created: 2024-02-09 Last update: 2025-09-16 12:30
2 security issues in trixie high

There are 2 open security issues in trixie.

2 important issues:
  • CVE-2025-59436: The ip (aka node-ip) package through 2.0.1 (in NPM) might allow SSRF because the IP address value 017700000001 is improperly categorized as globally routable via isPublic. NOTE: this issue exists because of an incomplete fix for CVE-2024-29415.
  • CVE-2025-59437: 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).
Created: 2025-09-16 Last update: 2025-09-16 12:30
2 security issues in sid high

There are 2 open security issues in sid.

2 important issues:
  • CVE-2025-59436: The ip (aka node-ip) package through 2.0.1 (in NPM) might allow SSRF because the IP address value 017700000001 is improperly categorized as globally routable via isPublic. NOTE: this issue exists because of an incomplete fix for CVE-2024-29415.
  • CVE-2025-59437: 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).
Created: 2025-09-16 Last update: 2025-09-16 12:30
2 security issues in forky high

There are 2 open security issues in forky.

2 important issues:
  • CVE-2025-59436: The ip (aka node-ip) package through 2.0.1 (in NPM) might allow SSRF because the IP address value 017700000001 is improperly categorized as globally routable via isPublic. NOTE: this issue exists because of an incomplete fix for CVE-2024-29415.
  • CVE-2025-59437: 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).
Created: 2025-09-16 Last update: 2025-09-16 12:30
3 security issues in bullseye high

There are 3 open security issues in bullseye.

1 important issue:
  • CVE-2025-59437: 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).
2 issues postponed or untriaged:
  • CVE-2023-42282: (needs triaging) The ip package before 1.1.9 for Node.js might allow SSRF because some IP addresses (such as 0x7f.1) are improperly categorized as globally routable via isPublic.
  • CVE-2024-29415: (needs triaging) The ip package through 2.0.1 for Node.js might allow SSRF because some IP addresses (such as 127.1, 01200034567, 012.1.2.3, 000:0:0000::01, and ::fFFf:127.0.0.1) are improperly categorized as globally routable via isPublic. NOTE: this issue exists because of an incomplete fix for CVE-2023-42282.
Created: 2025-09-16 Last update: 2025-09-16 12:30
debian/patches: 1 patch to forward upstream low

Among the 2 debian patches available in version 2.0.1+~1.1.3-3 of the package, we noticed the following issues:

  • 1 patch where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.
Created: 2023-02-26 Last update: 2025-04-23 14:31
news
[rss feed]
  • [2025-05-03] node-ip 2.0.1+~1.1.3-3 MIGRATED to testing (Debian testing watch)
  • [2025-04-23] Accepted node-ip 2.0.1+~1.1.3-3 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2024-05-29] Accepted node-ip 2.0.1+~1.1.3-2 (source) into experimental (Yadd) (signed by: Xavier Guimard)
  • [2024-05-01] node-ip 2.0.1+~1.1.3-1 MIGRATED to testing (Debian testing watch)
  • [2024-04-28] Accepted node-ip 2.0.1+~1.1.3-1 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2022-08-02] node-ip 2.0.0+~1.1.0-1 MIGRATED to testing (Debian testing watch)
  • [2022-07-27] Accepted node-ip 2.0.0+~1.1.0-1 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2021-12-13] node-ip 1.1.5+~1.1.0-1 MIGRATED to testing (Debian testing watch)
  • [2021-12-10] Accepted node-ip 1.1.5+~1.1.0-1 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2020-03-03] node-ip 1.1.5-5 MIGRATED to testing (Debian testing watch)
  • [2020-03-01] Accepted node-ip 1.1.5-5 (source) into unstable (Xavier Guimard)
  • [2020-03-01] Accepted node-ip 1.1.5-4 (source) into unstable (Xavier Guimard)
  • [2019-01-09] node-ip 1.1.5-3 MIGRATED to testing (Debian testing watch)
  • [2019-01-06] Accepted node-ip 1.1.5-3 (source) into unstable (Xavier Guimard)
  • [2019-01-04] Accepted node-ip 1.1.5-2 (source) into unstable (Andreas Moog) (signed by: Xavier Guimard)
  • [2018-04-12] node-ip REMOVED from testing (Debian testing watch)
  • [2018-01-15] node-ip 1.1.5-1 MIGRATED to testing (Debian testing watch)
  • [2018-01-04] Accepted node-ip 1.1.5-1 (source all) into unstable, unstable (suman) (signed by: Praveen Arimbrathodiyil)
bugs [bug history graph]
  • all: 0
links
  • homepage
  • lintian
  • buildd: logs, reproducibility
  • popcon
  • browse source code
  • edit tags
  • other distros
  • security tracker
  • screenshots
  • debian patches
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 2.0.1+~1.1.3-3

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing