# CVE-2024-29415: ip SSRF improper categorization in isPublic

> The ip library for Node.js incorrectly categorizes certain IP addresses as public, allowing Server-Side Request Forgery attacks.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2024
- **Updated:** 13 Feb 2025
- **Also known as:** CLSA-2026-1774657401, CLSA-2026-1792160906, DEBIAN-CVE-2024-29415, GHSA-2p57-rm9w-gvfp, MINI-8wm4-557r-8xf5, MINI-9gq3-34wx-wr7g, MINI-frjr-x6gq-6fmc, ROOT-APP-NPM-CVE-2024-29415, UBUNTU-CVE-2024-29415

## What is CVE-2024-29415?

CVE-2024-29415 is a high-severity server-side request forgery vulnerability in n/a, published on 27 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-941 (Incorrectly Specified Destination in a Communication Channel), CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2024-29415?

2 open source packages ship an affected version, including ip.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ip` | npm | All versions to 2.0.1 | None |
| `ip` | npm | All versions to 2.0.1 | None |

## How do I fix CVE-2024-29415?

Upgrade to a fixed version.

## Is CVE-2024-29415 being exploited?

There is no known exploitation of CVE-2024-29415 in the wild and no public exploit code.

Public exploit code:

- Sample project that uses VEX to supress CVE-2024-29415. (github_poc): https://github.com/felipecruz91/node-ip-vex
- Maintained fork of node-ip with the unpatched SSRF advisory (CVE-2024-29415) fixed (github_poc): https://github.com/bybraveHQ/ip2

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-29415 and fix it if it is affected.

What it is: CVE-2024-29415 is a high-severity server-side request forgery vulnerability in n/a, published on 27 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-29415 in the wild and no public exploit code.

Affected packages and fixed versions:
- ip (npm): affected all versions up to 2.0.1; no fix listed
- ip (npm): affected all versions up to 2.0.1; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-29415/ (Markdown: https://insights.sbomify.com/CVE-2024-29415/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-29415
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-29415
- OSV: https://osv.dev/vulnerability/CVE-2024-29415

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-29415/
Summaries are generated and may contain mistakes; the official description above is the record.
