Apache StreamPark: maven build params could trigger remote command execution

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.7 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L

EPSS

• CVE-2024-29737: 1.12% estimated exploitation activity in the next 30 days; percentile 66.14 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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/success2.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…

Published by the source

17 Jul 2024, 09:30 UTC

Last modified by the source

13 Feb 2025, 20:22 UTC

Source last checked

26 Oct 2026, 16:35 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5v69-92vw-fmjh

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-29737

Advisory: Apache StreamPark: maven build params could trigger remote command execution
IDs: CVE-2024-29737, GHSA-5v69-92vw-fmjh
Record: https://patchnext.com/advisories/cve-2024-29737 (revision 1, source checked 26 Oct 2026, 16:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.streampark:streampark 2.1.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.streampark:streampark: affected < 2.1.4; fixed in 2.1.4

## Suggested inspection (read-only)
- Maven org.apache.streampark:streampark: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.streampark:streampark.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5v69-92vw-fmjh (GitHub-reviewed advisory GHSA-5v69-92vw-fmjh lists affected ranges: Maven org.apache.streampark:streampark >=0 <2.1.4)

Commands are suggestions: review each one before running it.