What is CVE-2023-42282?

CVE-2023-42282 is a low-severity server-side request forgery (SSRF) vulnerability in ip (npm), affecting versions = 2.0.0. It is fixed in 2.0.1, 1.1.9. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.

Which versions of ip are affected by CVE-2023-42282?

ip (npm) versions = 2.0.0 is affected.

Is there a fix for CVE-2023-42282?

Yes. CVE-2023-42282 is fixed in 2.0.1, 1.1.9. Upgrade to this version or later.

Is CVE-2023-42282 exploitable, and should I be worried?

Whether CVE-2023-42282 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-42282 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2023-42282?

Upgrade: ip to 2.0.1 or later, ip to 1.1.9 or later.

CVE-2023-42282 in ip

Summary

NPM IP package incorrectly identifies some private IP addresses as public

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.

Impact

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

Affected versions

ip (= 2.0.0) ip (< 1.1.9)

Security releases

ip → 2.0.1 (npm) ip → 1.1.9 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

ip to 2.0.1 or later; ip to 1.1.9 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2023-42282? CVE-2023-42282 is a low-severity server-side request forgery (SSRF) vulnerability in ip (npm), affecting versions = 2.0.0. It is fixed in 2.0.1, 1.1.9. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
Which versions of ip are affected by CVE-2023-42282? ip (npm) versions = 2.0.0 is affected.
Is there a fix for CVE-2023-42282? Yes. CVE-2023-42282 is fixed in 2.0.1, 1.1.9. Upgrade to this version or later.
Is CVE-2023-42282 exploitable, and should I be worried? Whether CVE-2023-42282 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-42282 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2023-42282?
- Upgrade ip to 2.0.1 or later
- Upgrade ip to 1.1.9 or later

Other vulnerabilities in ip

CVE-IDSeverityPackage summary

CVE-2024-29415Highip: ip SSRF improper categorization in isPublic