NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

CVE-2023-42282 — ip

CRITICALFix: indutny/node-ip@6a3ada9

CVE-2023-42282 is a critical-severity (CVSS 9.8) Server-Side Request Forgery (SSRF) vulnerability in ip. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for ip — see the affected versions and patch details below.

NPM IP package incorrectly identifies some private IP addresses as public

Also known asGHSA-78xj-cgh5-2h22
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
2 known
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-42282.

EPSS Exploitation Probability

via FIRST.org ↗
1.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs76th percentile — riskier than 76% of all scored CVEsHighest risk
0.17%0.82%1.47%2.11%0.7%1.6%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

3Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
ipnpm
9.1Mdownloads / week

Description

The isPublic() function in the NPM package ip doesn't correctly identify certain private IP addresses in uncommon formats such as 0x7F.1 as private. Instead, it reports them as public by returning true. This can lead to security issues such as Server-Side Request Forgery (SSRF) if isPublic() is used to protect sensitive code paths when passed user input. Versions 1.1.9 and 2.0.1 fix the issue.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmip≥ 2.0.0&&< 2.0.12.0.1npm install ip@2.0.1
📦npmipall versions1.1.9npm install ip@1.1.9

Affected Products

1 product · 2 configurations
Application
ipfedorindutny
< 1.1.9
1 version
2.0.0
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ip, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update ip to 2.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-42282 is resolved across your whole dependency graph.

  3. Workarounds

    Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

It appears that npm does not utilize the bundled code therefore Red Hat Enterprise Linux is not affected by this vulnerability. While the vulnerability in the NPM IP Package presents a significant security concern, it's categorized as important rather than critical due to several factors. Firstly, the…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for CVE-2023-42282 (CC BY 4.0)
ProductFixed inAdvisory
HawtIO 4.0.0 for Red Hat build of Apache Camel 4see advisoryRHSA-2024:3550
Migration Toolkit for Virtualization 2.5migration-toolkit-virtualization/mtv-console-plugin-rhel9:2.5.6-4RHBA-2024:1440
NETWORK-OBSERVABILITY-1.6.0-RHEL-9network-observability/network-observability-cli-rhel9:v1.6.0-66RHSA-2024:3868
Red Hat OpenShift Dev Spaces 3 Containersdevspaces/code-rhel8:3.17-19RHSA-2024:10236
RHDH-1.1-RHEL-9rhdh/rhdh-hub-rhel9:1.1-97RHEA-2024:1366
RHODF-4.15-RHEL-9odf4/mcg-core-rhel9:v4.15.0-68RHSA-2024:1383

Frequently Asked Questions

The `isPublic()` function in the NPM package `ip` doesn't correctly identify certain private IP addresses in uncommon formats such as `0x7F.1` as private. Instead, it reports them as public by returning `true`. This can lead to security issues such as Server-Side Request Forgery (SSRF) if `isPublic()` is used to protect sensitive code paths when passed user input. Versions 1.1.9 and 2.0.1 fix the issue.
O3 Security · Impact-Aware SCA

Is CVE-2023-42282 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2023-42282: ip SSRF — Fixed in 2.0.1