# CVE-2024-25624: iris-web vulnerable to Server Side Template Injection in reports

> Authenticated administrators can inject malicious Jinja2 templates into reports, allowing any user to trigger remote code execution.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Apr 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-m64w-f7fg-hpcr

## What is CVE-2024-25624?

CVE-2024-25624 is a medium-severity code injection vulnerability in dfir-iris iris-web, published on 25 Apr 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Iris is a web collaborative platform aiming to help incident responders sharing technical details during investigations. Due to an improper setup of Jinja2 environment, reports generation in `iris-web` is prone to a Server Side Template Injection (SSTI). Successful exploitation of the vulnerability can lead to an arbitrary Remote Code Execution. An authenticated administrator has to upload a crafted report template containing the payload. Upon generation of a report based on the weaponized report, any user can trigger the vulnerability.  The vulnerability is patched in IRIS v2.4.6. No workaround is available. It is recommended to update as soon as possible. Until patching, review the report templates and keep the administrative privileges that include the upload of report templates limited to dedicated users.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

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

It affects 1 product.


Products: Dfir-Iris Iris.

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

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

## Is CVE-2024-25624 being exploited?

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

## Other vulnerabilities in dfir-iris iris-web

- [CVE-2026-22783](https://insights.sbomify.com/CVE-2026-22783/): Iris Allows Arbitrary File Deletion via Mass Assignment in Datastore File Management (critical 9.6)
- [CVE-2023-30615](https://insights.sbomify.com/CVE-2023-30615/): Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in iris-web (medium 6.3)
- [CVE-2024-25640](https://insights.sbomify.com/CVE-2024-25640/): Improper Neutralization of Alternate XSS Syntax in iris-web (medium 4.6)
- [CVE-2023-50712](https://insights.sbomify.com/CVE-2023-50712/): Improper Neutralization of Alternate XSS Syntax in iris-web (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-25624 is a medium-severity code injection vulnerability in dfir-iris iris-web, published on 25 Apr 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-25624 in the wild and no public exploit code.

Affected product: dfir-iris iris-web. 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-25624/ (Markdown: https://insights.sbomify.com/CVE-2024-25624/index.md)
```

## Sources

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

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