# CVE-2023-42282 (npm 'ip' package IP-validation flaw) reignites maintainer-vs-researcher CVE severity dispute

> JFrog's blog revisits CVE-2023-42282, a Critical-rated (CVSS 9.8) SSRF-enabling IP-validation flaw in the widely used npm 'ip' package's isPrivate()/isPublic() functions. Maintainer Fedor Indutny disputed the severity as theoretical and archived the repository in protest; GitHub subsequently downgraded the advisory to Low, reigniting the industry-wide debate over inflated CVE severity for dependency-risk vulnerabilities.

- **Published:** 2026-02-16T00:00:00Z
- **Last reviewed:** 2026-02-16T00:00:00Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-1536
- **Card image:** https://intel.threadlinqs.com/og/threat/threat-intel-npm-ip-ispublic-ssrf-bypass-tl-2026-1536.webp?v=ee6e4bce (Threadlinqs threat intel: CVE-2023-42282 npm ip Package SSRF: Detection & IOCs (TL-2026-1536) — Medium severity, 20 IOCs, 9 detection rules.)
- **ID:** TL-2026-1536
- **Severity:** MEDIUM (CVSS 9.8)
- **Category:** VULNERABILITY
- **Status:** TRACKING
- **Detections:** 9 (1 shown free below) · **IOCs:** 20
- **CVEs:** CVE-2023-42282

## Description

CVE-2023-42282 affects the `ip` npm package (maintained by Fedor Indutny, a former Node.js TSC member and Signal engineer), which is downloaded roughly 16-17 million times per week and has over 3,500 direct dependents. The flaw lives in the isPrivate()/isPublic() helper functions, which are meant to classify whether a given IP address string is a private (RFC1918/loopback/link-local) or public/globally-routable address. The isPublic() function is implemented simply as the negation of isPrivate() (!ip.isPrivate(addr)). The underlying isPrivate() logic fails to canonicalize non-standard numeric IP representations before comparing them against private CIDR ranges: hexadecimal-prefixed octets (e.g. 0x7f.1), octal-leading-zero octets (e.g. 017700000001), and pure 32-bit decimal/integer notation (e.g. 2130706433) are all valid ways operating-system network stacks and many URL parsers will resolve to 127.0.0.1 or other private/loopback addresses, but the `ip` package's regex/parsing logic does not recognize them as such and classifies them as public. An application that uses isPublic()/isPrivate() as an allow/deny gate before making an outbound HTTP request (a common SSRF-mitigation pattern) can therefore be tricked into contacting internal-only resources (localhost services, cloud metadata endpoints, internal APIs) by supplying an attacker-controlled, non-canonical IP string that the gate incorrectly treats as safe/public or fails to block as private, depending on how the check is wired. NVD assigned CVSS 3.1 9.8 (Critical, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and CWE-918 (Server-Side Request Forgery). Fixes shipped in `ip` 1.1.9 and 2.0.1, though a follow-up GitHub issue (#150) reported the isPublic() function still misclassified some private IPs as public even after the patch. Indutny publicly disputed the Critical rating, arguing that in the overwhelming majority of real-world call sites, the IP string passed into isPrivate()/isPublic() originates from the OS network stack (e.g. a socket's remote address) rather than from untrusted, attacker-supplied user input, making exploitation largely theoretical absent an unusual integration pattern. When npm audit and dependent-project bots began generating a wave of Critical-severity warnings/PRs across his and other projects, Indutny archived the node-ip GitHub repository (making it read-only) around June 25, 2024, as a protest against what he and other maintainers (echoing similar disputes over curl, micromatch, and Jackson) characterized as inflated, unverified CVE severities imposed on maintainers without their input into the scoring process. Other developers, including Jon Schlinkert (micromatch maintainer, itself subject to a similarly disputed high-severity CVE), publicly challenged researchers to demonstrate a real-world exploitable library/application rather than a purely theoretical call path. GitHub's Advisory Database subsequently revised the advisory's severity down to Low, and Indutny restored the repository about a week after the archival. The episode is widely cited (JFrog, BleepingComputer, Socket.dev) as a case study in the friction between automated/bounty-driven vulnerability disclosure pipelines (Snyk, Huntr, npm audit) and the maintainers who bear the reputational and support burden of disputed CVEs, and in the broader debate about whether CVSS base scores adequately account for real-world reachability/exploitability of a flaw versus its worst-case theoretical severity.

## MITRE ATT&CK

- T1190 Exploit Public-Facing Application
- T1195.001 Compromise Software Dependencies and Development Tools
- T1505 Server Software Component
- T1027 Obfuscated Files or Information
- T1685 Disable or Modify Tools
- T1580 Cloud Infrastructure Discovery
- T1016 System Network Configuration Discovery
- T1530 Data from Cloud Storage
- T1071.001 Web Protocols
- T1090.001 Internal Proxy
- T1552.005 Cloud Instance Metadata API
- T1489 Service Stop
- T1595.002 Vulnerability Scanning
- T1588.006 Vulnerabilities
- T1526 Cloud Service Discovery
- T1078.004 Cloud Accounts

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**Vulnerable npm 'ip' Package Version Installed/Loaded (CVE-2023-42282)** (`TL-2026-1536-SPL-002`)

Detects installation or module load of the npm 'ip' package at a version still affected by CVE-2023-42282 (< 1.1.9 on the 1.x line, < 2.0.1 on the 2.x line, or any version given the post-patch isPublic() bypass reported in Issue #150), surfaced via dependency-scanner output or file-system writes to node_modules/ip.

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1195.001, T1588.006
- **Data sources:** npm_audit_logs, dependency_scanner_logs, endpoint_file_events
- **Severity:** medium
- **Confidence:** high

### Splunk SPL

```spl
index=security sourcetype="npm:audit" OR sourcetype="dependency_scan"
| search (package_name="ip" OR advisory_id="GHSA-78xj-cgh5-2h22" OR cve="CVE-2023-42282")
| eval vulnerable=if(match(installed_version, "^1\.(0|1\.[0-8])$") OR installed_version="2.0.0" OR installed_version < "2.0.1", "true", "needs_review")
| table _time, host, project, package_name, installed_version, vulnerable, advisory_id
| sort -_time
```

### Microsoft KQL

```kql
let LookbackWindow = 7d;
DeviceFileEvents
| where TimeGenerated > ago(LookbackWindow)
| where FolderPath has "node_modules/ip" or FolderPath has "node_modules\\ip"
| where FileName in ("ip.js", "package.json")
| project TimeGenerated, DeviceName, FolderPath, FileName, InitiatingProcessFileName, InitiatingProcessCommandLine
| summarize Count=count(), FirstSeen=min(TimeGenerated), LastSeen=max(TimeGenerated) by DeviceName, FolderPath
```

### Sigma

```yaml
title: Node.js Process Loading node-ip Package Version Vulnerable to CVE-2023-42282
id: 3d5e7f9a-1b2c-4d6e-8f0a-9c1b3d5e7f9a
status: experimental
description: Detects a file event for node_modules/ip/lib/ip.js, the source path patched by CVE-2023-42282 (isPrivate/isPublic SSRF-gate bypass); combine with dependency-scanner version data to confirm exposure.
references:
    - https://github.com/indutny/node-ip/commit/6a3ada9b471b09d5f0f5be264911ab564bf67894
    - https://github.com/advisories/GHSA-78xj-cgh5-2h22
author: Threadlinqs Team
date: 2026-07-19
tags:
    - attack.resource-development
    - attack.t1588.006
    - cve.2023.42282
logsource:
    category: file_event
    product: linux
detection:
    selection:
        TargetFilename|contains: 'node_modules/ip/lib/ip.js'
    condition: selection
falsepositives:
    - Routine dependency installation of the ip package prior to remediation
level: low
```

**Known false positives:**

- Routine CI/CD dependency installs of the ip package prior to a scheduled remediation window
- Dev/sandbox environments not exposed to untrusted input

**Tuning notes:** Join file-event hits against SBOM/dependency-scanner version data to confirm the installed version is actually < 1.1.9/< 2.0.1 before alerting; suppress for environments already tracked as remediated in the SBOM inventory.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- Web Request Containing Hex/Octal/Decimal Loopback Alias (Sentinel) (locked: unlock with TL Creds)
- npm Dependency Scanner Alert for GHSA-78xj-cgh5-2h22 / CVE-2023-42282 (Sentinel) (locked: unlock with TL Creds)
- Node Process Egress to Cloud Metadata Endpoint Post-Validation Call (Sentinel) (locked: unlock with TL Creds)
- Sigma: Non-Canonical IP Notation Request Parameter (SSRF-Gate Bypass Probe) (locked: unlock with TL Creds)
- Sigma: Vulnerable node-ip Package File Present (CVE-2023-42282) (locked: unlock with TL Creds)
- Sigma: Node Process Connection to Loopback/IMDS Following Validation Call (locked: unlock with TL Creds)
- Non-Canonical IP Notation in Web Request Parameters (CVE-2023-42282 SSRF-Gate Bypass) (locked: unlock with TL Creds)
- Application Egress to Loopback/IMDS Address Immediately After SSRF Gate Check (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sources

- [Vulnerability or Not a Vulnerability?](https://jfrog.com/blog/vulnerability-or-not-a-vulnerability/)
- [CVE-2023-42282 Detail](https://nvd.nist.gov/vuln/detail/CVE-2023-42282)
- [NPM IP package incorrectly identifies some private IP addresses as public - GHSA-78xj-cgh5-2h22](https://github.com/advisories/GHSA-78xj-cgh5-2h22)
- [Dev rejects CVE severity, makes his GitHub repo read-only](https://www.bleepingcomputer.com/news/security/dev-rejects-cve-severity-makes-his-github-repo-read-only/)
- [node-ip Maintainer Restores GitHub Repo After Archiving Due to Overblown CVE Rating](https://socket.dev/blog/node-ip-maintainer-restores-github-repo-after-archiving-due-to-overblown-cve-rating)
- [Security Advisory: NPM ip package still incorrectly identifies some private IP addresses as public (Issue #150)](https://github.com/indutny/node-ip/issues/150)
- [NPM IP package incorrectly identifies some private IP addresses as public (Issue #147)](https://github.com/indutny/node-ip/issues/147)
- [HIGH Severity Vulnerability: Package unsafe for use as of v1.1.8 (Issue #136)](https://github.com/indutny/node-ip/issues/136)
- [Missing IP Address Control in isPublic() Function Leads to SSRF Bypass PoC](https://cosmosofcyberspace.github.io/npm_ip_cve/npm_ip_cve.html)
- [Huntr bounty report - ip package SSRF](https://huntr.com/bounties/bfc3b23f-ddc0-4ee7-afab-223b07115ed3/)
- [NetApp Security Advisory ntap-20240315-0008](https://security.netapp.com/advisory/ntap-20240315-0008/)
- [node-ip patch commit 6a3ada9](https://github.com/indutny/node-ip/commit/6a3ada9b471b09d5f0f5be264911ab564bf67894)
- [indutny/node-ip repository](https://github.com/indutny/node-ip)
- [CVE-2023-42282: NPM ip isPublic SSRF Bypass](https://www.miggo.io/vulnerability-database/cve/CVE-2023-42282)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-1536
