How severe is GHSA-78xj-cgh5-2h22?

No CVSS score has been assigned to GHSA-78xj-cgh5-2h22 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-78xj-cgh5-2h22?

GHSA-78xj-cgh5-2h22 affects the following packages: ip (npm), ip (npm). Ecosystems affected: npm.

How do I fix GHSA-78xj-cgh5-2h22?

Update ip to 2.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-78xj-cgh5-2h22 is resolved across your whole dependency graph.

How do I detect GHSA-78xj-cgh5-2h22 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ip. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-78xj-cgh5-2h22 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-78xj-cgh5-2h22?

O3 pinpoints whether GHSA-78xj-cgh5-2h22 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-78xj-cgh5-2h22 actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-78xj-cgh5-2h22, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-78xj-cgh5-2h22?

GHSA-78xj-cgh5-2h22 has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 73th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-78xj-cgh5-2h22?

GHSA-78xj-cgh5-2h22 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-78xj-cgh5-2h22 published, and has it been updated?

GHSA-78xj-cgh5-2h22 was published on February 8, 2024 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-78xj-cgh5-2h22

NPM IP package incorrectly identifies some private IP addresses as public

Also known asCVE-2023-42282

Published

Feb 8, 2024

Updated

Feb 4, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk73th percentile+0.94%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

ipnpm

9.4Mdownloads / 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

Ecosystem	Package	Vulnerable range	Fix
📦npm	`ip`	≥ 2.0.0&&< 2.0.1	2.0.1
📦npm	`ip`	all versions	1.1.9

Exploits & PoCs

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

The ip package before 1.1.9 for Node.js might allow SSRF because some IP…

cosmosofcyberspace.github.ioNVDFeb 2024

The ip package before 1.1.9 for Node.js might allow SSRF because some IP…

huntr.comNVDMar 2024

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ip. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update ip to 2.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-78xj-cgh5-2h22 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-78xj-cgh5-2h22 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-78xj-cgh5-2h22. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 GHSA-78xj-cgh5-2h22 in your dependencies?

O3 detects GHSA-78xj-cgh5-2h22 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works