# CVE-2024-29737: Apache StreamPark (incubating): maven build params could trigger remote command execution


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 17 Jul 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-5v69-92vw-fmjh

## What is CVE-2024-29737?

CVE-2024-29737 is a high-severity vulnerability in Apache StreamPark (incubating), published on 17 Jul 2024. 

### Official description

In streampark, the project module integrates Maven's compilation capabilities. The input parameter validation is not strict, allowing attackers to insert commands for remote command execution, The prerequisite for a successful attack is that the user needs to log in to the streampark system and have system-level permissions. Generally, only users of that system have the authorization to log in, and users would not manually input a dangerous operation command. Therefore, the risk level of this vulnerability is very low.

Mitigation:

all users should upgrade to 2.1.4

Background info:

Log in to Streampark using the default username (e.g. test1, test2, test3) and the default password (streampark). Navigate to the Project module, then add a new project. Enter the git repository address of the project and input `touch /tmp/success_2.1.2` as the "Build Argument". Note that there is no verification and interception of the special character "`". As a result, you will find that this injection command will be successfully executed after executing the build.

In the latest version, the special symbol ` is intercepted.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

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-29737?

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

## Is CVE-2024-29737 being exploited?

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

## Other vulnerabilities in Apache StreamPark (incubating)

- [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-2024-29178](https://insights.sbomify.com/CVE-2024-29178/): Apache StreamPark: FreeMarker SSTI RCE Vulnerability (high 8.8)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-29737 is a high-severity vulnerability in Apache StreamPark (incubating), published on 17 Jul 2024. 
Exploitation: There is no known exploitation of CVE-2024-29737 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-29737/ (Markdown: https://insights.sbomify.com/CVE-2024-29737/index.md)
```

## Sources

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

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