Server-Side Request Forgery (SSRF) Affecting strapi package, versions *
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-STRAPI-7323680
- published21 Jun 2024
- disclosed20 Jun 2024
- creditVaibhav Barkade
Introduced: 20 Jun 2024
CVE-2024-37818 (opens in a new tab)How to fix?
There is no fixed version for strapi.
Overview
strapi is a HTTP layer sits on top of Koa.
Affected versions of this package are vulnerable to Server-Side Request Forgery (SSRF) through the /strapi.io/_next/image component. This attack can be perform as an unauthorized user by simply sending GET request to the below endpoint, leading to sensitive data leakage, such as authorization credentials.
Workaround
Some means of remediation include:
Whitelists and DNS Resolution
Authentication on Internal Services
Harden Cloud Services
Response Handling
Disable Unused URL Schemas