Security readout for executives and security teams
Plain-English summary
Some Node.js applications may trust the ip package to decide whether a destination is public. Versions before 1.1.9 can misclassify certain loopback-style addresses as public, which can weaken SSRF defenses and expose internal services if the application fetches user-controlled URLs.
Executive priority
Treat as high-priority where Node.js applications use this package in SSRF defenses. The issue is critical by CVSS, but business urgency should be based on whether exposed services fetch attacker-controlled URLs.
Technical view
CVE-2023-42282 affects the Node.js ip package before 1.1.9. Its isPublic logic can incorrectly categorize some special IP representations as globally routable, creating an SSRF validation bypass in applications that rely on that result for access control.
Likely exposure
Exposure is most likely in Node.js services using ip before 1.1.9 to validate user-supplied URLs, proxy targets, webhook destinations, importers, or server-side fetch requests.
Exploitation context
The bundle does not show CISA KEV listing or confirmed active exploitation. Public discussion and references describe an SSRF validation weakness and a disputed severity context, so risk depends heavily on how applications use the library.
Researcher notes
The affected CPE data in the bundle is incomplete. Focus analysis on actual dependency presence and whether application logic treats isPublic as a security boundary. Avoid assuming all installations are exploitable.
Mitigation direction
- Inventory direct and transitive use of the Node.js ip package.
- Upgrade ip to version 1.1.9 or later where supported.
- Review SSRF controls that depend on ip.isPublic decisions.
- Use layered allowlists and network egress controls for server-side fetches.
- Check vendor advisories for affected downstream products.
- Prioritize internet-facing services that fetch user-controlled destinations.
Validation and detection
- Identify package-lock, yarn.lock, or pnpm-lock entries below ip 1.1.9.
- Search code for ip.isPublic use in request validation paths.
- Confirm URL fetch features cannot reach internal-only destinations.
- Review tests covering unusual IP formats and loopback handling.
- Check vendor appliances or products against published advisories.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-42282 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://cosmosofcyberspace.github.io/npm_ip_cve/npm_ip_cve.htmlCVE reference
- https://github.com/indutny/node-ip/commit/6a3ada9b471b09d5f0f5be264911ab564bf67894CVE reference
- https://huntr.com/bounties/bfc3b23f-ddc0-4ee7-afab-223b07115ed3/CVE reference
- https://security.netapp.com/advisory/ntap-20240315-0008/CVE reference
- https://www.bleepingcomputer.com/news/security/dev-rejects-cve-severity-makes-his-github-repo-read-only/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.