Skip to navigation

Threat reportVulnerabilityTL-2026-1536

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

mediumTRACKING

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.

Key facts

IdentifiersTL-2026-1536, CVE-2023-42282
Also known asnode-ip SSRF bypass, ip.isPublic() misclassification, GHSA-78xj-cgh5-2h22
SeverityMEDIUM
CVSS9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
EPSSCVE-2023-42282: 1.6% (75.2th percentile)
Affected productsFedor Indutny (indutny) ip (npm package / node-ip)
Weaknesses (CWE)CWE-918, CWE-1284
MITRE ATT&CK techniquesT1016 System Network Configuration Discovery, T1027 Obfuscated Files or Information, T1071.001 Web Protocols, T1078.004 Cloud Accounts, T1090.001 Internal Proxy, T1190 Exploit Public-Facing Application, T1195.001 Compromise Software Dependencies and Development Tools, T1489 Service Stop, T1505 Server Software Component, T1526 Cloud Service Discovery, T1530 Data from Cloud Storage, T1552.005 Cloud Instance Metadata API and 4 more in the attack flow
MotivationUNKNOWN
Target sectorssoftware-supply-chain, technology, saas, open-source-ecosystem
Target regionsGlobal
Detection rules9 (1 shown free)
Sources14 cited sources

Detection coverage

As of 2026-02-16, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-1536 across Splunk SPL, Microsoft KQL and Sigma, covering 20 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Vulnerable npm 'ip' Package Version Installed/Loaded (CVE-2023-42282)

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

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

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

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. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Web Request Containing Hex/Octal/Decimal Loopback Alias (Sentinel) · unlock with TL Creds
  • npm Dependency Scanner Alert for GHSA-78xj-cgh5-2h22 / CVE-2023-42282 (Sentinel) · unlock with TL Creds
  • Node Process Egress to Cloud Metadata Endpoint Post-Validation Call (Sentinel) · unlock with TL Creds
  • Sigma: Non-Canonical IP Notation Request Parameter (SSRF-Gate Bypass Probe) · unlock with TL Creds
  • Sigma: Vulnerable node-ip Package File Present (CVE-2023-42282) · unlock with TL Creds
  • Sigma: Node Process Connection to Loopback/IMDS Following Validation Call · unlock with TL Creds
  • Non-Canonical IP Notation in Web Request Parameters (CVE-2023-42282 SSRF-Gate Bypass) · unlock with TL Creds
  • Application Egress to Loopback/IMDS Address Immediately After SSRF Gate Check · unlock with TL Creds

Indicators of compromise

As of 2026-02-16, Threadlinqs Intelligence tracks 20 indicators of compromise for TL-2026-1536.

20 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

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 techniques by tactic:

Discovery

T1016 System Network Configuration Discovery; T1526 Cloud Service Discovery; T1580 Cloud Infrastructure Discovery

Defense Evasion

T1027 Obfuscated Files or Information

Command and Control

T1071.001 Web Protocols; T1090.001 Internal Proxy

Initial Access

T1078.004 Cloud Accounts; T1190 Exploit Public-Facing Application; T1195.001 Compromise Software Dependencies and Development Tools

Impact

T1489 Service Stop

persistence

T1505 Server Software Component

Collection

T1530 Data from Cloud Storage

Credential Access

T1552.005 Cloud Instance Metadata API

Resource Development

T1588.006 Vulnerabilities

Reconnaissance

T1595.002 Vulnerability Scanning

defense-impairment

T1685 Disable or Modify Tools

Remediation

Patches

  • ip@1.1.9 (patches CVE-2023-42282 for the 1.x branch)
  • ip@2.0.1 (patches CVE-2023-42282 for the 2.x branch)

Immediate actions

  • Upgrade the npm 'ip' package to >= 1.1.9 (1.x line) or >= 2.0.1 (2.x line) to receive the CVE-2023-42282 patch
  • Do not rely solely on ip.isPrivate()/ip.isPublic() as an SSRF allow/deny gate for attacker-influenced input; treat the check as defense-in-depth only
  • Canonicalize/normalize IP address strings (reject non-decimal-dotted-quad forms such as hex, octal, or pure integer notation) before any network-boundary trust decision

Workarounds

  • Wrap isPublic()/isPrivate() calls with prior normalization that rejects any address string not in strict dotted-decimal IPv4 or standard IPv6 notation
  • Pin egress traffic through a proxy that resolves and validates the final IP independent of the application's own IP-classification logic

Longer-term hardening

  • Adopt a maintained, actively-patched IP-parsing library and monitor its advisory history before depending on niche validation helpers for security-relevant decisions
  • Implement SSRF defenses at the network layer (egress allow-listing, metadata service protections such as IMDSv2/hop-limit, dedicated proxy with DNS pinning) rather than relying on application-level string parsing alone
  • Track the maintainer/consumer friction highlighted by this incident when triaging future dependency CVEs: verify real-world reachability of the vulnerable code path in your own call sites before treating a Critical CVSS score as an automatic P0

Affected and fixed versions

  • Fedor Indutny (indutny) — ip (npm package / node-ip)
    Vulnerable versions: <= 1.1.8; 2.0.0
    Fixed in: 1.1.9; 2.0.1 (isPublic() bypass reported to persist in issue #150 after these fixes)

Timeline

  • Security researcher reports to Huntr/GitHub that the ip package's isPrivate()/isPublic() functions misclassify non-standard IP notations (hex, octal, decimal) as public, tracked as CVE-2023-42282 and filed against versions <= 1.1.8 (GitHub Issue #136).
  • Maintainer Fedor Indutny ships a patch commit (6a3ada9) addressing the reported misclassification, released in ip 1.1.9.
  • NVD publishes CVE-2023-42282 with a Critical CVSS 3.1 base score of 9.8 (CWE-918, SSRF); GitHub Advisory Database publishes GHSA-78xj-cgh5-2h22 listing versions <= 2.0.0 (and < 1.1.9) as affected.
  • NetApp publishes advisory ntap-20240315-0008 tracking exposure to CVE-2023-42282 in NetApp products bundling the affected npm dependency.
  • GitHub Issue #150 reports that isPublic() still incorrectly classifies some private IP addresses as public even after the 1.1.9/2.0.1 patches, and notes the package is effectively unmaintained.
  • Indutny publicly disputes the Critical severity rating on Mastodon, arguing exploitation is largely theoretical since IP input typically originates from the OS network stack rather than untrusted user input, and archives the node-ip GitHub repository (read-only) in protest against automated npm-audit noise generated by the CVE.
  • BleepingComputer publishes coverage of the dispute, drawing parallels to similar CVE-severity disputes over curl, micromatch, and Jackson, and quoting micromatch maintainer Jon Schlinkert challenging researchers to show a real-world exploitable case.
  • GitHub's Advisory Database revises the GHSA-78xj-cgh5-2h22 severity rating down from Critical to Low following Indutny's public feedback and review of real-world reachability.
  • Indutny restores the node-ip GitHub repository to normal (non-read-only) status approximately one week after archiving it, following the severity downgrade.
  • Socket.dev publishes a detailed retrospective analyzing the incident as a case study in maintainer-vs-researcher friction and CVE scoring process gaps, including commentary from Stacklok's Evan Anderson on disclosure-driven 'clout-chasing'.
  • JFrog publishes a blog post revisiting CVE-2023-42282 as a case study in the broader 'is it a vulnerability or not' debate, prompting this threat-intel harness entry.

Sources cited

Previous and next in vulnerability

Drafted by the Threadlinqs research pipeline from 14 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats