# CVE-2024-29178: Apache StreamPark: FreeMarker SSTI RCE Vulnerability

> Authenticated attackers can achieve remote code execution on Apache StreamPark servers via FreeMarker template injection.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Jul 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-vv8h-m63v-53pq

## What is CVE-2024-29178?

CVE-2024-29178 is a high-severity code injection vulnerability in Apache StreamPark, published on 18 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

On versions before 2.1.4, a user could log in and perform a template injection attack resulting in Remote Code Execution on the server, The attacker must successfully log into the system to launch an attack, so this is a moderate-impact vulnerability.

Mitigation:

all users should upgrade to 2.1.4

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

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

2 open source packages ship an affected version, including org.apache.streampark:streampark. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.streampark:streampark` | Maven | All versions | 2.1.4 |
| `org.apache.streampark:streampark` | Maven | All versions | 2.1.4 |

Products: Apache Streampark.

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

Upgrade org.apache.streampark:streampark to 2.1.4 or later.

## Is CVE-2024-29178 being exploited?

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

## Other vulnerabilities in Apache StreamPark

- [CVE-2022-45802](https://insights.sbomify.com/CVE-2022-45802/): Apache StreamPark (incubating): Upload any file to any directory (critical 9.8)
- [CVE-2024-29070](https://insights.sbomify.com/CVE-2024-29070/): Apache StreamPark: session not invalidated after logout (critical 9.1)
- [CVE-2022-46365](https://insights.sbomify.com/CVE-2022-46365/): Apache StreamPark (incubating): Logic error causing any account reset (critical 9.1)
- [CVE-2023-52291](https://insights.sbomify.com/CVE-2023-52291/): Apache StreamPark (incubating): Unchecked maven build params could trigger remote command execution (high 8.8)
- [CVE-2024-29737](https://insights.sbomify.com/CVE-2024-29737/): Apache StreamPark (incubating): maven build params could trigger remote command execution (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-29178 is a high-severity code injection vulnerability in Apache StreamPark, published on 18 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-29178 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.streampark:streampark (Maven): affected all versions; fixed in 2.1.4
- org.apache.streampark:streampark (Maven): affected all versions; fixed in 2.1.4

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

## Sources

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

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