Server-Side Request Forgery (SSRF) Affecting nossrf package, versions <1.0.4
Threat Intelligence
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.
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-NOSSRF-9510842
- published23 Mar 2025
- disclosed23 Mar 2025
- creditLiran Tal
Introduced: 23 Mar 2025
NewCVE-2025-2691 (opens in a new tab)How to fix?
Upgrade nossrf to version 1.0.4 or higher.
Overview
Affected versions of this package are vulnerable to Server-Side Request Forgery (SSRF) where an attacker can provide a hostname that resolves to a local or reserved IP address space and bypass the SSRF protection mechanism.
PoC
- Define an
app.jsfile with the programmatic API ofnossrfas follows:
const nossrf = require("nossrf") const main = async()=> { let is_safe = await nossrf.asyncValidateUrl("https://google.com") // true means good console.log(is_safe)let is_safe2 = await nossrf.asyncValidateUrl("https://localtest.me") // true means good console.log(is_safe2)}
main()
Run the
app.jsfileValidate that the localtest.me hostname resolves to a local IP address space 127.0.0.1 and the SSRF protection mechanism is bypassed since for both of the two URLs the response is true