Server-Side Request Forgery (SSRF) Affecting ssrfcheck package, versions <1.2.0
Threat Intelligence
Exploit Maturity
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
Proof of Concept
Do your applications use this vulnerable package?
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 applicationsSnyk Learn
Learn about Server-Side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-SSRFCHECK-9510756
- published27 Jul 2025
- disclosed23 Mar 2025
- creditLiran Tal
Introduced: 23 Mar 2025
CVE-2025-8267 (opens in a new tab)Common Vulnerabilities and Exposures (CVE) are common identifiers for publicly known security vulnerabilities
Common Weakness Enumeration (CWE) is a category system for software weaknesses
How to fix?
Upgrade ssrfcheck to version 1.2.0 or higher.
Overview
Affected versions of this package are vulnerable to Server-Side Request Forgery (SSRF) due to an incomplete denylist of IP address ranges. Specifically, the package fails to classify the reserved IP address space 224.0.0.0/4 (Multicast) as invalid. This oversight allows attackers to craft requests targeting these multicast addresses.
PoC
import { isSSRFSafeURL } from 'ssrfcheck';
let result
result = isSSRFSafeURL('https://012.1.2.3/whatever');
console.log(result); // returns false
result = isSSRFSafeURL('https://localhost:8080/whatever');
console.log(result); // returns false
result = isSSRFSafeURL('https://239.255.255.250:8080/whatever');
console.log(result); // returns true - bypassed