Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsLearn about Server-Side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learningThere is no fixed version for private-ip
.
private-ip is a Check if IP address is private.
Affected versions of this package are vulnerable to Server-Side Request Forgery (SSRF) where an attacker can provide an IP or hostname that resolves to a multicast IP address (224.0.0.0/4) which is not included as part of the private IP ranges in the package's source code.
import is_ip_private from 'private-ip' import ipaddr from 'ipaddr.js'
// -- private-ip console.log(is_ip_private('127.0.0.1')) console.log(is_ip_private('10.0.0.0')) console.log(is_ip_private('169.254.0.1')) console.log(is_ip_private('239.255.255.250'))
// -- ipaddr.js console.log(ipaddr.parse('127.0.0.1').range()) console.log(ipaddr.parse('10.0.0.0').range()) console.log(ipaddr.parse('169.254.0.1').range()) console.log(ipaddr.parse('239.255.255.250').range())
Run the app.js file
Observe that the private-ip package does not detect the multicast IP address 239.255.255.250
as a private IP address and returns true
for all 4 checks.