StackPrism

npm package

ip 0.0.5 vulnerabilities, and what to upgrade to

ip 0.0.5 has 2 known vulnerabilities (1 rated high or critical); 1.1.9 fixes 1 of them, and 1 has no fixed version yet. 1.1.9 has 1 known vulnerability of its own, and so does every newer release we checked.

npm (opens in a new tab) describes it as “[![](https://badge.fury.io/js/ip.svg)](https://www.npmjs.com/package/ip)”

Known vulnerabilities
2
1 rated high or critical
Released
Feb 20, 2013
Latest is 2.0.1
Downloads last week
539
Under 1% of ip downloads
Licence
MIT
OpenSSF Scorecard
2.6/10
indutny/node-ip (opens in a new tab)
Dependencies
None
Resolved by deps.dev

What to upgrade to

Every newer release we checked still has known vulnerabilities. The fewer, the better.

  • 1.1.9

    Fixes 1 of the 2 known vulnerabilities. Released Feb 19, 2024.

    1 known vulnerability, worst rated warning

  • 2.0.1

    Latest release. Released Feb 19, 2024.

    1 known vulnerability, worst rated warning

Hand the fix to your coding agent

One task with the upgrade, the file to change and why. Paste it into Claude Code, Cursor or Codex.

Findings

Every advisory for ip 0.0.5

Known exploited first (CISA KEV), then by how likely they are to be exploited (FIRST EPSS), then by severity. Each id links to its OSV.dev record.

  1. CriticalCVE-2024-29415 on OSV.dev (opens in a new tab)GHSA-2p57-rm9w-gvfpEPSS: top 6%

    ip SSRF improper categorization in isPublic

    No fixed version listed yet. Published Jun 2, 2024.

  2. LowCVE-2023-42282 on OSV.dev (opens in a new tab)GHSA-78xj-cgh5-2h22EPSS: top 25%

    NPM IP package incorrectly identifies some private IP addresses as public

    Fixed in 1.1.9. Published Feb 8, 2024.

Who is still on a vulnerable ip

100% of last week’s 8M ip downloads went to versions with known vulnerabilities.

From npm’s per-version download counts for the last 7 days, each version checked against OSV.dev. The versions checked cover over 99% of downloads.

Is ip the only one?

Paste a public GitHub repo or drop your package.json and see every vulnerable, end-of-life or deprecated dependency, with one fix task. Free, no sign-up.

Check your whole repo

How this page is checked

StackPrism asks OSV.dev which advisories affect exactly ip 0.0.5, merges duplicates filed under several ids, and ranks them with CISA’s Known Exploited Vulnerabilities list and FIRST EPSS. Release dates and deprecation come from deps.dev and npm. No AI writes this page: every sentence comes from that data, refreshed every few hours.

Last checked against npm, OSV.dev, deps.dev, CISA KEV and FIRST EPSS.