# CVE-2024-7093: Server-Side Template Injection in Dispatch Message Templates

> Attackers can execute arbitrary code via unsanitized Jinja templates in Dispatch notification messages, leading to remote code execution.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2024
- **Updated:** 2 Aug 2024

## What is CVE-2024-7093?

CVE-2024-7093 is a critical code injection vulnerability in Netflix Dispatch, published on 1 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Dispatch's notification service uses Jinja templates to generate messages to users. Jinja permits code execution within blocks, which were neither properly sanitized nor sandboxed. This vulnerability enables users to construct command line scripts in their custom message templates, which are then executed whenever these notifications are rendered and sent out.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2024-7093 being exploited?

There is no known exploitation of CVE-2024-7093 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-7093 is a critical code injection vulnerability in Netflix Dispatch, published on 1 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-7093 in the wild and no public exploit code.

Affected product: Netflix Dispatch. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-7093/ (Markdown: https://insights.sbomify.com/CVE-2024-7093/index.md)
```

## Sources

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

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