# CVE-2024-37818: Strapi Server-Side Request Forgery (SSRF)

> Attackers can perform Server-Side Request Forgery via the image component to scan ports or access sensitive information, though the vendor disputes the validity of this issue.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2024
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-p9ff-j98v-p435

## What is CVE-2024-37818?

CVE-2024-37818 is a high-severity server-side request forgery vulnerability in n/a, published on 20 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Strapi v4.24.4 was discovered to contain a Server-Side Request Forgery (SSRF) via the component /strapi.io/_next/image. This vulnerability allows attackers to scan for open ports or access sensitive information via a crafted GET request. NOTE: The Strapi Development Community argues that this issue is not valid. They contend that "the strapi/admin was wrongly attributed a flaw that only pertains to the strapi.io website, and which, at the end of the day, does not pose any real SSRF risk to applications that make use of the Strapi library."

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2024-37818?

2 open source packages ship an affected version, including @strapi/strapi. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@strapi/strapi` | npm | All versions | None |
| `@strapi/strapi` | npm | All versions | None |

Products: Strapi Strapi.

## How do I fix CVE-2024-37818?

No fix has been published for CVE-2024-37818 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-37818 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-37818 exists.

## Other vulnerabilities in n/a

- [CVE-2023-22894](https://insights.sbomify.com/CVE-2023-22894/): Strapi Cleartext Storage of Sensitive Information (high 7.2, exploited in the wild)
- [CVE-2023-22621](https://insights.sbomify.com/CVE-2023-22621/): Strapi plugins vulnerable to Server-Side Template Injection and Remote Code Execution in the Users-Permissions Plugin (critical 10.0)
- [CVE-2022-27263](https://insights.sbomify.com/CVE-2022-27263/): Unrestricted Upload of File with Dangerous Type in Strapi (critical 9.8)
- [CVE-2020-27664](https://insights.sbomify.com/CVE-2020-27664/): Authorization bypass in Strapi (critical 9.8)
- [CVE-2019-18818](https://insights.sbomify.com/CVE-2019-18818/): Strapi allows unauthenticated attacker to reset admin password without valid reset token (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-37818 and fix it if it is affected.

What it is: CVE-2024-37818 is a high-severity server-side request forgery vulnerability in n/a, published on 20 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-37818 exists.

Affected packages and fixed versions:
- @strapi/strapi (npm): affected all versions; no fix listed
- @strapi/strapi (npm): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-37818/ (Markdown: https://insights.sbomify.com/CVE-2024-37818/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-37818
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-37818
- OSV: https://osv.dev/vulnerability/CVE-2024-37818

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-37818/
Summaries are generated and may contain mistakes; the official description above is the record.